From: Johannes Schindelin Date: Thu, 03 Apr 2008 19:14:39 GMT Subject: Re: [PATCH] git-clone.txt: Adjust note to --shared for new pruning behavior of git-gc Message-ID: In-Reply-To: <47F52145.306@nrlssc.navy.mil> Hi, On Thu, 3 Apr 2008, Brandon Casey wrote: > diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt > index 9758243..d3ab00b 100644 > --- a/Documentation/git-clone.txt > +++ b/Documentation/git-clone.txt > @@ -65,10 +65,12 @@ OPTIONS > + > *NOTE*: this is a possibly dangerous operation; do *not* use > it unless you understand what it does. If you clone your > -repository using this option, then delete branches in the > -source repository and then run linkgit:git-gc[1] using the > -'--prune' option in the source repository, it may remove > -objects which are referenced by the cloned repository. > +repository using this option and then delete branches in the > +source repository, some objects may become unreferenced (or dangling). > +These objects may be removed by normal git operations (such as git-commit[1]) > +which automatically call git-gc[1]. If these objects are removed and > +were referenced by the cloned repository, then the cloned repository > +will become corrupt. Please note that if you delete a branch _after_ running git-gc, the next git-gc would remove those objects anyway, since the first git-gc packed the objects, and they were therefore no longer dangling. So it was an issue before the new git-gc behaviour anyway. Ciao, Dscho