Matthieu Moy wrote:
Andreas Ericsson <ae@xxxxxx> writes:
Originally I was trying to find the lost tip, which was made impossible due to
the extremely large number of loose branch-tips git-lost-found reported.
[...]
Seems like an awful lot of trouble. I'll look into patching
builtin-pack-objects.c instead to accept an "--ignore-reflog" flag and prune
reflog-accessible objects.
Then, you'll most likely prune the branch you were looking for, won't
you?
I would obviously not use the flag when I'm looking for things, but when I'm
cleaning up after a workday when I *know* that everything is where it's
supposed to be, as it will then let me use git-lost-found to find the single
loose tip I'm interested in rather than having to wade through the 500+ lines
of cruft in the reflog.
No offence to the reflog inventors. It's a great thing to have to prevent
users from screwing up their repos, but it sucks that you can't disable its
use without either deleting it entirely or manually moving it around prior
to the action where you want it to be ignored.
--
Andreas Ericsson andreas.ericsson@xxxxxx
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
-
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
