summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 8c667f4)
raw | patch | inline | side by side (parent: 8c667f4)
author | Junio C Hamano <junkio@cox.net> | |
Fri, 9 Dec 2005 00:30:24 +0000 (16:30 -0800) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Fri, 9 Dec 2005 00:30:24 +0000 (16:30 -0800) |
Not replacing but always including our own refs may be more
desirable (and unarguably much safer), but at the same time I
have a suspicion that that might be forbidding a useful usage I
haven't thought of, so...
Signed-off-by: Junio C Hamano <junkio@cox.net>
desirable (and unarguably much safer), but at the same time I
have a suspicion that that might be forbidding a useful usage I
haven't thought of, so...
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/git-prune.txt | patch | blob | history |
index 3367c9b21452db7e73ec29f03d36fd2d11b56b97..05c8d4928e4869f5297cf35146a2c2fb167b9062 100644 (file)
SYNOPSIS
--------
-'git-prune' [-n]
+'git-prune' [-n] [--] [<head>...]
DESCRIPTION
-----------
Do not remove anything; just report what it would
remove.
+--::
+ Do not interpret any more arguments as options.
+
+<head>...::
+ Instead of keeping objects
+ reachable from any of our references, keep objects
+ reachable from only listed <head>s.
++
+Note that the explicitly named <head>s are *not* appended to the
+default set of references, but they replace them. In general you
+would want to say `git prune $(git-rev-parse --all) extra1
+extra2` to keep chains of commits leading to extra1, extra2,
+... in addition to what are reachable from your own refs.
+Saying `git prune extra1 extra2` would *lose* objects reachable
+only from the usual refs, which is usually not what you want.
+
+
+EXAMPLE
+-------
+
+To prune objects not used by your repository and another that
+borrows from your repository via its
+`.git/objects/info/alternates`:
+
+------------
+$ git prune $(git-rev-parse --all) \
+ $(cd ../another && $(git-rev-parse --all))
+------------
Author
------