Petr Baudis <pasky@xxxxxxx> wrote: > Yes, I agree that this really is a problem, but that's a fundamental > limitation. At least for StGIT-maintained floating branches the latest > bleeding edge StGIT could fix that. (Except that the problem outlined by > Linus is present here as well, first prune will wipe your older patch > versions and your patch log will be useless - Catalin? Can we store the > older patch versions references in something like > .git/refs/patches-old/?) And except that it does that only for you - > there should be a way to conveniently mirror (clone+pull) the patch > stack setup. Why not change reflog to store the last n values or the last n days (obtained from .git/config file) as refs under refs/prior-heads ? I can see the same concept of ref history being useful even for core git-rebase and doing it this way would also give it to StGIT without Catalin needing to change code. But it doesn't help git bisect. Of course a looooong time ago when I first implemented reflog support this was suggested but not implemented at the time due to the high cost per ref. Now that we have Linus' packed refs available this may not be nearly as much of a problem. -- Shawn. - 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