Re: [PATCH] Use git-update-ref in scripts.

From: Junio C Hamano <junkio@cox.net>
Date: Sep 28, 2005, 17:29 UTC
Message-ID: <7v3bnpt81e.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.58.0509281007200.3308@g5.osdl.org>

Linus Torvalds <torvalds@osdl.org> writes:

> Heh. My kernel has none of that. Well, it obviously has refs, but even 
> there it literally has just one head: "master". The rest are the standard 
> tags you see in public.

I was wondering the URL shorthand you mentioned is being used in practice. In theory, you do not "have to write out in full" anymore ;-).

Message-ID: <Pine.LNX.4.58.0507151529590.19183@g5.osdl.org>
From: Linus Torvalds <torvalds@osdl.org>
Date: Fri, 15 Jul 2005 15:42:42 -0700 (PDT)

And it's not necessarily just the branch handling, but more of a generic shorthand: I'd love to be able to mix something like

	git pull jgarzik/misc-2.6 upstream

and "jgarzik" would be expanded (through something like .git/branches) to "master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/"), resulting in the _full_ path being expanded to

	master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/misc-2.6 upstream

which I have to write out in full (or, more commonly, cut-and-paste) right now.