There is a scenario when using git clone -s and git gc --prune togother is dangerous. Document this. Signed-off-by: Miklos Vajna <vmiklos@xxxxxxxxxxxxxx> --- On Tue, Jan 22, 2008 at 03:10:10PM -0600, Brandon Casey <casey@xxxxxxxxxxxxxxx> wrote: > I find that second sentence hard to understand. Maybe: > > 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. Here is the re-worded version. Documentation/git-clone.txt | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-) diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt index fdccbd4..2341881 100644 --- a/Documentation/git-clone.txt +++ b/Documentation/git-clone.txt @@ -62,6 +62,14 @@ OPTIONS .git/objects/info/alternates to share the objects with the source repository. The resulting repository starts out without any object of its own. + *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. + + --reference <repository>:: If the reference repository is on the local machine -- 1.5.4.rc3.4.g16335-dirty - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
