Re: [PATCH 0/4] Pulling refs files

From: Petr Baudis <pasky@ucw.cz>
Date: May 13, 2005, 23:37 UTC
Message-ID: <20050513233738.GL32232@pasky.ji.cz>
In-Reply-To: <Pine.LNX.4.21.0505131853020.30848-100000@iabervon.org>

Dear diary, on Sat, May 14, 2005 at 01:14:22AM CEST, I got a letter where Daniel Barkalow <barkalow@iabervon.org> told me that...

Show 19 quoted lines

> On Sat, 14 May 2005, Petr Baudis wrote:
> 
> > 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?
> 
> The point is to specify the commit to pull by fetching a file from the
> other side, not just to move a file. So you need to be specifying that the
> file is a hex encoding of the sha1 hash of the starting point of the pull,
> and the refs/ area is where these are expected to be. (Note that it still
> doesn't have any knowledge about the meanings of files in refs/; you tell
> it which one you want to use, and optionally which one you want to write
> to, and it will use the names you provide).
> 
> It wouldn't help much to download the head file if you had to know the
> contents of that file already in order to do everything as a single
> transfer.

So what about just something like

	git-wormhole-pull remote:refs/head/master wormhole://localhost/

That is, you could just specify remote:path_relative_to_url instead of SHA1 id as the commit.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor