From: "Matthias Andree" <matthias.andree@gmx.de>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v3] To make GIT-VERSION-FILE, search for git more widely
Date: Wed, 13 May 2009 14:17:09 +0200 [thread overview]
Message-ID: <op.utva2vxh1e62zd@balu> (raw)
In-Reply-To: <7vskje6wsy.fsf@alter.siamese.dyndns.org>
Am 09.05.2009, 18:55 Uhr, schrieb Junio C Hamano <gitster@pobox.com>:
> "Matthias Andree" <matthias.andree@gmx.de> writes:
>
>>> Fine then. Or you could just append "." to the $PATH ;-)
>>
>> "." in the super user's PATH? Cool stuff, and so innovative.
>
> I didn't mean to suggest PATH=$PATH:. *in the user's environment* ;-).
> You do that inside GIT-VERSION-FILE, which is essentially the same thing
> as running ./git$X from there.
No, it is not -- the scope of the GIT variable is much narrower than doing
PATH=$PATH:. in the script.
BTW, in the earlier version, I used type(1) to take $PATH search into
account in case GIT=git; test -x does not do path search, unlike type.
> What's innovative is whoever is running build as root.
Yes, and that is why I found the PATH-dependent behaviour so irritating
and wanted to fix it. I have another approach cooking that entails
factoring out common code from ./git-gui/GIT-VERSION-GEN and
./GIT-VERSION-GEN into ./git-gui/GIT-VERSION-SUBR.
For any approach taken, we'll have to touch both the shell and the
Makefile, unless we want to manually redo things in the GIT-VERSION-GEN
script that were already done automatically or programmatically in
Makefile.
Please let me know if you're willing to accept a patch that touches both
Makefile and the GIT-VERSION-* shell scripts. If you don't, I can quit
here and not waste further time on submissions that are inacceptable
anyhow, but just keep rebasing my local patch instead.
Best regards
--
Matthias Andree
next prev parent reply other threads:[~2009-05-13 12:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 9:22 [PATCH v3] To make GIT-VERSION-FILE, search for git more widely Matthias Andree
2009-05-07 11:49 ` Michael J Gruber
2009-05-07 12:04 ` Matthias Andree
2009-05-07 12:09 ` Michael J Gruber
2009-05-07 12:12 ` Matthias Andree
2009-05-08 0:05 ` Junio C Hamano
2009-05-08 8:27 ` Matthias Andree
2009-05-08 8:41 ` Junio C Hamano
2009-05-08 11:09 ` Matthias Andree
2009-05-09 16:55 ` Junio C Hamano
2009-05-09 17:10 ` Francis Galiegue
2009-05-09 18:17 ` Matthias Andree
2009-05-13 12:17 ` Matthias Andree [this message]
2009-05-13 19:32 ` Junio C Hamano
2009-06-02 10:55 ` Nanako Shiraishi
2009-06-02 15:50 ` Junio C Hamano
2009-06-02 18:35 ` Johannes Sixt
2009-06-03 7:32 ` Matthias Andree
2009-06-04 0:12 ` [PATCH v4] " Matthias Andree
2009-06-04 5:18 ` [PATCH v3] " Junio C Hamano
2009-06-04 8:35 ` Matthias Andree
2009-05-08 8:52 ` Johannes Sixt
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=op.utva2vxh1e62zd@balu \
--to=matthias.andree@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).