From: Andreas Ericsson <ae@op5.se>
To: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] C implementation of the 'git' program.
Date: Thu, 10 Nov 2005 23:50:16 +0100 [thread overview]
Message-ID: <4373CEA8.1020900@op5.se> (raw)
In-Reply-To: <Pine.LNX.4.64.0511101133550.4627@g5.osdl.org>
Linus Torvalds wrote:
>
> And the performance difference does seem to be quite noticeable too..
>
Yes. I was quite astonished when I noticed first, thinking the shell
kept the parsed script in cache or some such. Apparently it doesn't.
>
>>The location of the GIT_LIB can be obtained by running
>>
>> git --lib
>
>
> I think this might be a bit ambiguous. When I see "GIT_LIB", to me it
> implies traditional libraries (ie a "libgit.a" kind of thing), not the
> kind of "git executable plugin" directory.
>
> So I'd suggest renaming "--lib" and "GIT_LIB" to be more of a "--libexec"
> kind of flavor, if only to avoid that confusion.
Someone said libexec was moving out (of Linux, at least), so I thought
I'd better avoid that. Perhaps GIT_LIBDIR?
Btw, I re-visited ye ole "git binary directory?" thread and noticed the
nifty trick you did with PATH from the wrapper. I'll add that to git.c
and, unless I get a better suggestion, rename GIT_LIB to GIT_LIBDIR (and
git --libdir).
> Even if the actual
> directory ends up being /usr/lib/git-<version>/ as in my original
> suggestion, I think it's good to make it clear that it's not just some
> kind of "link type" library, but more of a combination of libraries and
> plugins and executables.
>
> But maybe that's just me?
>
It's not just you, but GIT_DIR was taken and I felt lazy.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2005-11-10 22:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 18:26 [PATCH] C implementation of the 'git' program Andreas Ericsson
2005-11-10 19:41 ` Linus Torvalds
2005-11-10 22:50 ` Andreas Ericsson [this message]
2005-11-10 23:37 ` Petr Baudis
2005-11-11 19:31 ` Junio C Hamano
2005-11-11 6:58 ` Raja R Harinath
2005-11-11 7:40 ` Junio C Hamano
2005-11-11 12:04 ` Andreas Ericsson
2005-11-11 19:37 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4373CEA8.1020900@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.