Re: git binary directory?

From: Petr Baudis <pasky@suse.cz>
Date: Nov 7, 2005, 00:43 UTC
Message-ID: <20051107004346.GR1431@pasky.or.cz>
In-Reply-To: <7virv5wc86.fsf@assigned-by-dhcp.cox.net>

Dear diary, on Mon, Nov 07, 2005 at 01:08:57AM CET, I got a letter where Junio C Hamano <junkio@cox.net> told me that...

Show 12 quoted lines

> Petr Baudis <pasky@suse.cz> writes:
> 
> > You are also going to break the porcelains (w/o manual user
> > intervention), so I'm not happy about it but if you are doing it, do it
> > now, please. :-)
> 
> I thought Porcelains and people's script can just say 'git foo'
> everywhere where it currently says 'git-foo', and it should work
> before and after the change, and that is what I did to my
> private scripts.  But you are right, it is nicer if 'git-foo'
> continued to work with a single patch to cg-Xlib or somewhere
> central like that.

I want to avoid extra fork()s and exec()s. They seem to routinely matter in orders of magnitude of speed in tight loops.

Besides, I'm more used to the dash form. ;-)

> > BTW, can I easily get the patch from the 'git' tool, so that I can
> > extend $PATH appropriately during Cogito initialization?
> 
> Do you mean 'git --show-git-libdir' or something like that?

Yes. Well... you said you have the gitdir changes in your 'pu' branch, but http://www.kernel.org/git/?p=git/git.git;a=tree;h=pu;hb=pu doesn't appear to have the changes...?

Is --show-git-libdir already implemented?

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.