From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: junkio@cox.net, git@vger.kernel.org
Subject: Re: [PATCH 3/2] git-merge-cache -q doesn't complain about failing merge program
Date: Fri, 29 Jul 2005 19:11:21 -0700 [thread overview]
Message-ID: <7vack582ly.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20050729125338.GB21909@pasky.ji.cz
Petr Baudis <pasky@suse.cz> writes:
> git-merge-cache reporting failed merge program is undesirable for
> Cogito, since it emits its own more appropriate error message in that
> case. However, I want to show other possible git-merge-cache error
> messages. So -q will just silence this particular error.
That description makes it sound more like it is a Cogito
specific hack, which other Porcelains may not benefit from,
meaning they may want to suppress some other errors but this
patch does not give that possibility.
I do not mind about the above too much, but I'll sit on this one
for now just in case if anybody comes up with a different patch
to give a bit cleaner solution.
I wonder how many die()'s we have in our C code. It _might_ be
cleaner to say (the first parameter being exit(2) parameter):
die("unable to execute '%s'", pgm);
die_with(47, "merge program failed");
and have the calling Porcelain, if it wants to, supress error
messages by redirecting 2>/dev/null, and say whatever it wants
to say based on $?.
next prev parent reply other threads:[~2005-07-30 2:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 8:58 [PATCH 0/2] Bits from git-pb Petr Baudis
2005-07-29 9:00 ` [PATCH 1/2] Trivial tidyups Petr Baudis
2005-07-29 9:01 ` [PATCH 2/2] Unify usage strings declaration Petr Baudis
2005-07-30 2:11 ` Junio C Hamano
2005-07-30 6:03 ` Matthias Urlichs
2005-07-29 12:53 ` [PATCH 3/2] git-merge-cache -q doesn't complain about failing merge program Petr Baudis
2005-07-30 2:11 ` Junio C Hamano [this message]
2005-07-29 15:48 ` [PATCH 4/2] Improve the compilation-time settings interface Petr Baudis
2005-07-29 18:23 ` Petr Baudis
2005-07-29 15:48 ` [PATCH 5/2] Remove the explicit Makefile dependencies description Petr Baudis
2005-07-29 15:50 ` [PATCH 6/2] Reorder Makefile rules Petr Baudis
2005-07-29 15:50 ` [PATCH 7/2] Support for NO_OPENSSL Petr Baudis
2005-07-30 3:39 ` Linus Torvalds
2005-07-30 4:17 ` Junio C Hamano
2005-07-30 5:02 ` [PATCH] Under NO_OPENSSL -lssl should not be used Junio C Hamano
2005-07-30 16:09 ` Linus Torvalds
2005-08-02 22:43 ` Jon Seymour
2005-07-29 17:21 ` [PATCH 8/2] Build commands through object files Petr Baudis
2005-07-30 10:31 ` [PATCH 0/2] Bits from git-pb Petr Baudis
2005-07-30 17:33 ` Junio C Hamano
2005-07-30 17:59 ` 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=7vack582ly.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.