Re: [PATCH 0/4] Pulling refs files
- From
Petr Baudis <pasky@ucw.cz>
- Date
- May 13, 2005, 22:19 UTC
- Message-ID
- <20050513221935.GC32232@pasky.ji.cz>
- In-Reply-To
- <Pine.LNX.4.21.0505130245260.30848-100000@iabervon.org>
Dear diary, on Fri, May 13, 2005 at 08:49:25AM CEST, I got a letter where Daniel Barkalow <barkalow@iabervon.org> told me that...
Show 10 quoted lines
> This series makes the following changes: > > 1: Adds support for having the C code know about the general existance of > .git/refs, and functions for writing these files. > 2: Adds support in the generic pull code for fetching refs (and dummy > implementations). > 3: Adds support in the HTTP pull code for fetching refs > 4: Adds support in the rsh pull code for fetching refs; this requires > changes to the protocol. These changes should be sufficient to support > any future extension, however.
Hmm, I've honestly expected something different - a generic way to specify any file in the repository to be pulled along, instead of a introducing refs awareness at this level of git. What would be the advantages of that approach against just specifying list of other files to pull along?
-- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor