Re: [PATCH 5/5] remote: use exact HEAD lookup if it is available
- From
Jeff King <peff@peff.net>
- Date
- Feb 15, 2009, 19:58 UTC
- Message-ID
- <20090215195826.GA26740@coredump.intra.peff.net>
- In-Reply-To
- <20090215061818.GE30414@coredump.intra.peff.net>
On Sun, Feb 15, 2009 at 01:18:18AM -0500, Jeff King wrote:
> A possible 6/5 would be to do something similar for local repos (or > resurrecting the HEAD proposal).
Here is a quick and dirty series to unambiguously determine the HEAD for local repos, but I am undecided on whether this is actually a good idea.
Note that this fails Jay's tests in t5505 which expect the ambiguity; to be considered for inclusion, it would need to test "../two" as a remote as well as "file://$(pwd)/../two", making sure each behaved correctly.
But I am posting it here to stimulate discussion on whether it is even something we want.
1/2: transport: cleanup duplicated ref fetching code 2/2: transport: unambiguously determine local HEAD
-Peff