Junio C Hamano [off-list ref] writes:
Nikolai Weibull [off-list ref] writes:
quoted
The documentation for git-prune was lacking descriptions of the head
arguments and the -- option.
+<head>...::
+ The heads to look for unreachable objects in. This is
+ relative to $GIT_DIR (e.g., "HEAD", "refs/heads/master").
+ When unspecified, all heads are updated to match the
+ remote repository.
? updated to match???
Come to think of it, why would anybody want to pass heads
explicitly? It seems to me that it would allow you to _lose_
objects referenced only from omitted branches...
Junio C Hamano wrote:
Junio C Hamano [off-list ref] writes:
quoted
Nikolai Weibull [off-list ref] writes:
quoted
quoted
The documentation for git-prune was lacking descriptions of the head
arguments and the -- option.
+<head>...::
+ The heads to look for unreachable objects in. This is
+ relative to $GIT_DIR (e.g., "HEAD", "refs/heads/master").
+ When unspecified, all heads are updated to match the
+ remote repository.
quoted
? updated to match???
Come to think of it, why would anybody want to pass heads explicitly?
It seems to me that it would allow you to _lose_ objects referenced
only from omitted branches...
Sorry. I have no idea why I pasted in that description. How about:
<head>...::
A head to use for an unreachability trace.
(This mimics the description of <object> in git-fsck-objects.)
nikolai
--
Nikolai Weibull: now available free of charge at http://bitwi.se/!
Born in Chicago, IL USA; currently residing in Gothenburg, Sweden.
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}