From: Michael Schubert <mschub@elegosoft.com>
To: Sebastian Schuberth <sschuberth@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git alias fails if non-accessible directory is in PATH
Date: Sun, 08 May 2011 18:15:25 +0200 [thread overview]
Message-ID: <4DC6C19D.4060704@elegosoft.com> (raw)
In-Reply-To: <iq5p6k$73f$1@dough.gmane.org>
> Is this by design, or a bug? I currently do not see a reason for git stop executing an alias just because it cannot access a directory in PATH. Strangely, I also haven't found any discussion about this on the mailing list yet.
If you look at start_command(), `git br` ends up as execvp call
returning EACCESS in the given case whereas only ENOENT was "expected".
This happens before git tries to resolve the alias.
Could it be a legit assumption that PATH holds only accessible paths?
(POSIX?) Otherwise it's a bug.
next prev parent reply other threads:[~2011-05-08 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 9:53 git alias fails if non-accessible directory is in PATH Sebastian Schuberth
2011-05-08 16:15 ` Michael Schubert [this message]
2011-05-08 16:50 ` Junio C Hamano
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=4DC6C19D.4060704@elegosoft.com \
--to=mschub@elegosoft.com \
--cc=git@vger.kernel.org \
--cc=sschuberth@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).