From: Jeff King <peff@peff.net>
To: Unknown <borg@uu3.net>
Cc: git@vger.kernel.org
Subject: Re: [commit 4ecbc178704] Incosistency?
Date: Tue, 14 Jul 2009 17:48:52 -0400 [thread overview]
Message-ID: <20090714214852.GA2786@coredump.intra.peff.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0907142335210.31779@cube>
On Tue, Jul 14, 2009 at 11:41:40PM +0200, Unknown wrote:
> commit 4ecbc178704ca6c1027a38483e98f5fe493b1322
> Author: Jeff King <peff@peff.net>
> Date: Thu Jul 9 02:37:35 2009 -0400
>
> bla bla.. some strange SUDO fix (who the hell uses git that way?)
> I dont like it.. git-add in libexecdir was good!
Hmm. I think I wrote a better commit message than that...
> - { for p in $(filter-out git-add$X,$(BUILT_INS)); do \
> + ln "$$bindir/git$X" "$$execdir/git$X" 2>/dev/null || \
> + cp "$$bindir/git$X" "$$execdir/git$X"; } && \
> + { for p in $(BUILT_INS); do \
> $(RM) "$$execdir/$$p" && \
> - ln "$$execdir/git-add$X" "$$execdir/$$p" 2>/dev/null || \
> - ln -s "git-add$X" "$$execdir/$$p" 2>/dev/null || \
> - cp "$$execdir/git-add$X" "$$execdir/$$p" || exit; \
> + ln "$$execdir/git$X" "$$execdir/$$p" 2>/dev/null || \
> + ln -s "git$X" "$$execdir/$$p" 2>/dev/null || \
> + cp "$$execdir/git$X" "$$execdir/$$p" || exit; \
> done; } && \
> ./check_bindir "z$$bindir" "z$$execdir" "$$bindir/git-add$X"
>
> Isnt check_bindir is broken now?
> git-add is no more..
No. Two things you are missing:
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?).
2. check_bindir is actually about looking for dashed-form commands in
the $bindir, which would indicate cruft from an older installed
version of git. We can't use "git" for this, because that is the
command that is _supposed_ to be in $bindir.
-Peff
next prev parent reply other threads:[~2009-07-14 21:49 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 [this message]
2009-07-14 22:30 ` Johannes Schindelin
2009-07-15 8:32 ` Unknown
2009-07-15 9:42 ` Jeff King
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=20090714214852.GA2786@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).