{"thread":{"id":"13510","subject":"[PATCH] Updating documentation to match Brandon Casey's proposed git-repack patch.","startedAt":"2008-05-14T07:25:14Z","lastAt":"2008-05-14T08:26:26Z","messageCount":2,"participants":["Chris Frey","Johannes Schindelin"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"76923","messageId":"20080514072514.GA26202@foursquare.net","threadId":"13510","inReplyTo":null,"subject":"[PATCH] Updating documentation to match Brandon Casey's proposed git-repack patch.","fromName":"Chris Frey","fromEmail":"cdfrey@foursquare.net","sentAt":"2008-05-14T07:25:14Z","receivedAt":"2008-05-14T07:25:14Z","isPatch":true,"sender":{"key":"cdfrey@foursquare.net","avatar":null},"body":"I haven't heard any negative commentary on this patch, and I see\nthe repack patch is in next, so resending in case it was missed.\n\nThis patch clarifies the git-prune man page, documenting that it only\nprunes unpacked objects.  git-repack is documented according to\nthe new git-repack -A behaviour, which does not depend on\ngit-pack-objects --keep-unreachable anymore.\n\nSigned-off-by: Chris Frey <cdfrey@foursquare.net>\n---\n Documentation/git-prune.txt  |    5 ++++-\n Documentation/git-repack.txt |   14 +++++++++++++-\n 2 files changed, 17 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-prune.txt b/Documentation/git-prune.txt\nindex f92bb8c..3178bc4 100644\n--- a/Documentation/git-prune.txt\n+++ b/Documentation/git-prune.txt\n@@ -18,12 +18,15 @@ git-prune. See the section \"NOTES\", below.\n \n This runs `git-fsck --unreachable` using all the refs\n available in `$GIT_DIR/refs`, optionally with additional set of\n-objects specified on the command line, and prunes all\n+objects specified on the command line, and prunes all unpacked\n objects unreachable from any of these head objects from the object database.\n In addition, it\n prunes the unpacked objects that are also found in packs by\n running `git prune-packed`.\n \n+Note that unreachable, packed objects will remain.  If this is\n+not desired, see linkgit:git-repack[1].\n+\n OPTIONS\n -------\n \ndiff --git a/Documentation/git-repack.txt b/Documentation/git-repack.txt\nindex 3d95749..906d3c7 100644\n--- a/Documentation/git-repack.txt\n+++ b/Documentation/git-repack.txt\n@@ -8,7 +8,7 @@ git-repack - Pack unpacked objects in a repository\n \n SYNOPSIS\n --------\n-'git-repack' [-a] [-d] [-f] [-l] [-n] [-q] [--window=N] [--depth=N]\n+'git-repack' [-a] [-A] [-d] [-f] [-l] [-n] [-q] [--window=N] [--depth=N]\n \n DESCRIPTION\n -----------\n@@ -37,6 +37,18 @@ OPTIONS\n \tleaves behind, but `git fsck --full` shows as\n \tdangling.\n \n+-A::\n+\tSame as `-a`, but any unreachable objects in a previous\n+\tpack become loose, unpacked objects, instead of being\n+\tleft in the old pack.  Unreachable objects are never\n+\tintentionally added to a pack, even when repacking.\n+\tWhen used with '-d', this option\n+\tprevents unreachable objects from being immediately\n+\tdeleted by way of being left in the old pack and then\n+\tremoved.  Instead, the loose unreachable objects\n+\twill be pruned according to normal expiry rules\n+\twith the next linkgit:git-gc[1].\n+\n -d::\n \tAfter packing, if the newly created packs make some\n \texisting packs redundant, remove the redundant packs.\n-- \n1.5.4.4\n"},{"id":"76930","messageId":"alpine.DEB.1.00.0805140925060.30431@racer","threadId":"13510","inReplyTo":"20080514072514.GA26202@foursquare.net","subject":"Re: [PATCH] Updating documentation to match Brandon Casey's proposed git-repack patch.","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2008-05-14T08:26:26Z","receivedAt":"2008-05-14T08:26:26Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Wed, 14 May 2008, Chris Frey wrote:\n\n> I haven't heard any negative commentary on this patch, and I see\n> the repack patch is in next, so resending in case it was missed.\n\nThis part, together with the subject, is not really meant for application \nas-is, is it?  Please follow the guidelines for SubmittingPatches, and \nwrite supporting arguments that are not meant to be part of the commit \nmessages _after_ the \"---\".\n\nCiao,\nDscho\n"}]}