From: jrnieder@uchicago.edu
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Alex Riesen <raa.lkml@gmail.com>, Jeff King <peff@peff.net>
Subject: Re: [RFC/PATCH] Documentation: Don't assume git-sh-setup and git-parse-remote are in the PATH
Date: Sun, 29 Jun 2008 11:10:20 -0500 (CDT) [thread overview]
Message-ID: <Pine.GSO.4.62.0806291026310.8371@harper.uchicago.edu> (raw)
In-Reply-To: <20080629053823.GA8262@sigill.intra.peff.net>
On Sun, 29 Jun 2008, Jeff King wrote:
> I think the right question is:
>
> PATH=$PATH:$(git --exec-path)
> . git-sh-setup
>
> or
>
> . "$(git --exec-path)/git-sh-setup"
>
> ?
>
> Generally, I would prefer the latter because it has no side effects.
On Sun, 28 Jun 2008, Alex Riesen wrote:
> . "$(git --exec-path)/git-sh-setup"
I agree. I was blindly following the instructions from the release notes
to Git 1.5.4. After thinking about it a little and reading git-sh-setup.sh
and git-parse-remote.sh, it does seem safe not to add the exec-path to PATH.
How about this documentation patch? (This time tested! With hg-fast-export
appropriately modified:
$ hg clone http://hg.sharesource.org/asciidoc
$ mkdir asciidoc-git && cd asciidoc-git
$ git init && hg-fast-export.sh -r /path/to/asciidoc --quiet
$ git checkout
$ sudo ./install.sh
$ cd /path/to/git/Documentation && make git-{sh-setup,parse-remote}.html
I haven't tried rebuilding manpages, though.)
Junio: I stole the commit message from you. I hope you don't mind.
-- %< --
Subject: [PATCH] Documentation: don't assume git-sh-setup and git-parse-remote are in PATH
When git-parse-remote and git-sh-setup are not installed in
$(bindir) anymore, the shell script library won't be found on
user's $PATH in general.
Signed-off-by: Jonathan Nieder <jrnieder@uchicago.edu>
---
Documentation/git-parse-remote.txt | 2 +-
Documentation/git-sh-setup.txt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-parse-remote.txt b/Documentation/git-parse-remote.txt
index 951dbd6..421312e 100644
--- a/Documentation/git-parse-remote.txt
+++ b/Documentation/git-parse-remote.txt
@@ -8,7 +8,7 @@ git-parse-remote - Routines to help parsing remote repository access parameters
SYNOPSIS
--------
-'. git-parse-remote'
+'. "$(git --exec-path)/git-parse-remote"'
DESCRIPTION
-----------
diff --git a/Documentation/git-sh-setup.txt b/Documentation/git-sh-setup.txt
index c543170..6731f9a 100644
--- a/Documentation/git-sh-setup.txt
+++ b/Documentation/git-sh-setup.txt
@@ -7,7 +7,7 @@ git-sh-setup - Common git shell script setup code
SYNOPSIS
--------
-'git-sh-setup'
+'. "$(git --exec-path)/git-sh-setup"'
DESCRIPTION
-----------
--
1.5.5.1.328.gbfcc6
next prev parent reply other threads:[~2008-06-29 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 20:10 [RFC/PATCH] Documentation: Don't assume git-sh-setup and git-parse-remote are in the PATH Jonathan Nieder
2008-06-28 20:58 ` Alex Riesen
2008-06-28 21:05 ` Junio C Hamano
2008-06-29 5:38 ` Jeff King
2008-06-29 16:10 ` jrnieder [this message]
2008-06-29 19:08 ` Junio C Hamano
2008-06-30 2:39 ` Jonathan Nieder
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=Pine.GSO.4.62.0806291026310.8371@harper.uchicago.edu \
--to=jrnieder@uchicago.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=raa.lkml@gmail.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).