From: John Ellson <ellson@research.att.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Make GIT-VERSION-GEN tolerate missing git describe command
Date: Fri, 30 Dec 2005 14:31:56 -0500 [thread overview]
Message-ID: <dp41ve$v7r$1@sea.gmane.org> (raw)
In-Reply-To: <dp3mtp$rfm$1@sea.gmane.org>
John Ellson wrote:
> I think it is probably a bug that "git non_existent_command"
> returns its error message to stdout without an error, where
> "git-non_existent_command" behaves differently and does return an
> error.
BTW. Its the old shell-script version of "git" that fails to return an error on
non_existent_commands. The newer C version of "git" correctly returns an
error code.
The reason that this is a sufficiently serious problem to require a fix is that
the broken version of "git" is in the git-core-0.99.9a-2.fc5.i386.rpm that is
currently in Fedora Core Extras development.
John
next prev parent reply other threads:[~2005-12-30 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 16:23 [PATCH] Make GIT-VERSION-GEN tolerate missing git describe command John Ellson
2005-12-30 18:49 ` Linus Torvalds
2005-12-30 19:12 ` John Ellson
2005-12-30 19:55 ` Linus Torvalds
2005-12-30 19:31 ` John Ellson [this message]
2005-12-31 0:15 ` H. Peter Anvin
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='dp41ve$v7r$1@sea.gmane.org' \
--to=ellson@research.att.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).