From: Jeff King <peff@peff.net>
To: Unknown <borg@uu3.net>
Cc: git@vger.kernel.org
Subject: Re: [commit 4ecbc178704] Incosistency?
Date: Wed, 15 Jul 2009 05:42:52 -0400 [thread overview]
Message-ID: <20090715094252.GA26048@coredump.intra.peff.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0907151028050.10773@cube>
On Wed, Jul 15, 2009 at 10:32:32AM +0200, Unknown wrote:
> > 1. "git-add" still goes in exec-dir. It's just not the magic one we do
> > separately (see how we no longer need to use filter-out?).
> Right. but git-add now is a link to git. Now we have one more file
> out there.
Sorry, I don't understand the significance. Is having 'git' in the
execdir causing some kind of problem?
I agree that it shouldn't be necessary for most sane setups, but sadly
there are some insane ones, and I don't think this solution should be
hurting anyone else. Am I wrong?
-Peff
next prev parent reply other threads:[~2009-07-15 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 21:41 [commit 4ecbc178704] Incosistency? Unknown
2009-07-14 21:48 ` Jeff King
2009-07-14 22:30 ` Johannes Schindelin
2009-07-15 8:32 ` Unknown
2009-07-15 9:42 ` Jeff King [this message]
2009-07-17 17:42 ` Unknown
2009-07-14 22:42 ` Thomas Adam
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=20090715094252.GA26048@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=borg@uu3.net \
--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).