Alex Riesen <raa.lkml@gmail.com> writes:

quoted text
> If that will be the case git-p4-import.bat (yes, just a script of
> mine) will break because it has its namespace directly in $GIT_DIR
> (i.e. .git/p4/*) and stores there backup references. It is just a
> someones (ok, it is mine) script, but maybe there are others, who
> expect that plumbing level git-update-ref just do what its told.

That makes me realize that rejecting anything other than what I
suggested is a good idea, as it avoids mistakes like the one you
just made.  The fact is, that things that are reachable only
from .git/p4/* are subject to be pruned.  I'd suggest you move
them to somewhere under .git/refs, say, .git/refs/p4/*.

Neither ORIG_HEAD and FETCH_HEAD protects objects for the same
reason (although HEAD does).  And that is actually what we want,
as "git fetch" followed immediately by "git prune" should be
able to get rid of what was fetched.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html