From: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
To: Johannes Sixt <J.Sixt@eudaptics.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] bisect: use update-ref to update refs
Date: Wed, 28 Mar 2007 16:10:23 +0200 [thread overview]
Message-ID: <20070328141023.GB23378@informatik.uni-freiburg.de> (raw)
In-Reply-To: <460A71A1.D1388D3@eudaptics.com>
Johannes Sixt wrote:
> Uwe Kleine-König wrote:
> > GIT_DIR="$GIT_DIR" git-$command ...
> >
> > where the assignment to GIT_DIR should be superfluous?
>
> git-sh-setup sets GIT_DIR, but does not export it. Therefore, this
> assignment is *not* superfluous (its effect is to export GIT_DIR for
> this command only).
..., but why do only two invocations of git get GIT_DIR="$GIT_DIR" and
the other 20+ don't?
Best regards
Uwe
--
Uwe Kleine-König
http://www.google.com/search?q=sine+of+%2830+degree%29
prev parent reply other threads:[~2007-03-28 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 12:35 [PATCH] bisect: use update-ref to update refs Uwe Kleine-König
2007-03-28 13:46 ` Johannes Sixt
2007-03-28 14:10 ` Uwe Kleine-König [this message]
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=20070328141023.GB23378@informatik.uni-freiburg.de \
--to=ukleinek@informatik.uni-freiburg.de \
--cc=J.Sixt@eudaptics.com \
--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 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).