Brandon Casey a83c88525e t7700: demonstrate misbehavior of 'repack -a' when local packs exist
The ability to "...fatten [the] local repository by packing everything that
is needed by the local ref into a single new pack, including things that are
borrowed from alternates"[1] is supposed to be provided by the '-a' or '-A'
options to repack when '-l' is not used, but there is a flaw.  For each
pack in the local repository without a .keep file, repack supplies a
--unpacked=<pack> argument to pack-objects.

The --unpacked option to pack-objects, with or without an argument, causes
pack-objects to ignore any object which is packed in a pack not mentioned
in an argument to --unpacked=.  So, if there are local packs, and
'repack -a' is called, then any objects which reside in packs accessible
through alternates will _not_ be packed.  If there are no local packs, then
no --unpacked argument will be supplied, and repack will behave as expected.

[1] http://mid.gmane.org/7v8wrwidi3.fsf@gitster.siamese.dyndns.org

Signed-off-by: Brandon Casey <casey@nrlssc.navy.mil>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-01-17 23:44:33 -08:00
2008-11-27 19:25:06 -08:00
2008-12-17 21:56:48 -08:00
2009-01-17 23:07:19 -08:00
2009-01-13 23:12:51 -08:00
2008-12-03 21:29:03 -08:00
2008-10-26 16:21:08 -07:00
2008-10-21 17:58:11 -07:00
2008-12-07 15:13:02 -08:00
2008-10-08 08:05:43 -07:00
2008-11-08 21:33:55 -08:00
2008-12-07 15:13:02 -08:00
2008-09-25 09:39:24 -07:00
2009-01-13 00:14:55 -08:00
2009-01-17 23:08:53 -08:00
2009-01-05 13:01:01 -08:00
2008-10-10 08:39:20 -07:00
2008-10-10 08:39:20 -07:00
2009-01-05 13:01:01 -08:00
2009-01-07 00:10:14 -08:00
2008-11-02 16:36:40 -08:00
2009-01-11 13:21:57 -08:00
2008-11-14 19:11:49 -08:00
2008-11-11 14:49:50 -08:00
2009-01-01 05:48:40 -08:00
2008-12-03 14:27:17 -08:00
2008-12-17 20:15:17 -08:00
2009-01-17 23:05:34 -08:00
2008-09-25 08:00:28 -07:00
2008-12-07 15:13:02 -08:00
2008-11-23 19:23:34 -08:00
2008-10-25 12:09:31 -07:00
2008-12-15 23:06:13 -08:00
2008-11-11 14:49:50 -08:00
2009-01-11 13:21:57 -08:00
2008-11-14 22:12:38 -08:00
2008-10-09 11:26:17 -07:00
2008-09-29 07:30:16 -07:00

////////////////////////////////////////////////////////////////

	GIT - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, depending on your mood.

 - random three-letter combination that is pronounceable, and not
   actually used by any common UNIX command.  The fact that it is a
   mispronunciation of "get" may or may not be relevant.
 - stupid. contemptible and despicable. simple. Take your pick from the
   dictionary of slang.
 - "global information tracker": you're in a good mood, and it actually
   works for you. Angels sing, and a light suddenly fills the room.
 - "goddamn idiotic truckload of sh*t": when it breaks

Git is a fast, scalable, distributed revision control system with an
unusually rich command set that provides both high-level operations
and full access to internals.

Git is an Open Source project covered by the GNU General Public License.
It was originally written by Linus Torvalds with help of a group of
hackers around the net. It is currently maintained by Junio C Hamano.

Please read the file INSTALL for installation instructions.
See Documentation/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands,
and "man git-commandname" for documentation of each command.
CVS users may also want to read Documentation/cvs-migration.txt.

Many Git online resources are accessible from http://git.or.cz/
including full documentation and Git related tools.

The user discussion and development of Git take place on the Git
mailing list -- everyone is welcome to post bug reports, feature
requests, comments and patches to git@vger.kernel.org. To subscribe
to the list, send an email with just "subscribe git" in the body to
majordomo@vger.kernel.org. The mailing list archives are available at
http://marc.theaimsgroup.com/?l=git and other archival sites.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
Description
No description provided
Readme 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%