Re: [PATCH 0/4] Pulling refs files
- From
Junio C Hamano <junkio@cox.net>
- Date
- May 16, 2005, 07:55 UTC
- Message-ID
- <7v4qd3pptd.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <Pine.LNX.4.21.0505151129200.30848-100000@iabervon.org>
>>>>> "DB" == Daniel Barkalow <barkalow@iabervon.org> writes:
DB> On Sat, 14 May 2005, Junio C Hamano wrote:
Show 5 quoted lines
>> I am having a bit hard time understanding how the end user uses >> what you are trying to give them. Is the basic idea to let them >> say "I want to get Pasky's $GIT_DIR/refs/heads/master and store >> it in my $GIT_DIR/refs/heads/git-pb, and then I want to start >> the pull starting from the commit recorded in that ref"?
DB> Yes. This would be: git-http-pull -w heads/git-pb heads/master DB> http://www.kernel.org/pub/scm/cogito/git-pb.git/
That would be quite handy. IIRC, Pasky had a gripe about limiting this under refs hierarchy (that's why you can write "heads/master" in your example not "refs/heads/master", though), and I am sympathetic to it. Giving unlimited download access anywhere under foobar.git/ would be fine. About the receiving side, letting things to be written anywhere the user wants would also be fine.
Since this will all be scripted anyway, I do not mind if the above example needs to be spelled as:
$ git-http-pull -w ${GIT_DIR-.git}/refs/heads/git-pb refs/heads/master \
http://www.kernel.org/pub/scm/cogito/git-pb.git/