From: Junio C Hamano <gitster@pobox.com>
To: Ben Walton <bwalton@artsci.utoronto.ca>
Cc: bebarino@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH] ls-files: die instead of fprintf/exit in -i error
Date: Thu, 08 Oct 2009 23:53:12 -0700 [thread overview]
Message-ID: <7v1vld5a93.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 1255053215-14059-1-git-send-email-bwalton@artsci.utoronto.ca
Ben Walton <bwalton@artsci.utoronto.ca> writes:
> This is the alternate solution to this bug as proposed earlier today.
> I don't have a preference either way for which solution is better or
> more inline with the 'git way,' so please choose the most appropriate.
I think die() is better for consistency reasons if nothing else.
Thanks.
prev parent reply other threads:[~2009-10-09 6:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 14:20 [PATCH] ls-files: make option parser keep argv[0] Ben Walton
2009-10-08 20:32 ` Stephen Boyd
2009-10-09 1:53 ` [PATCH] ls-files: die instead of fprintf/exit in -i error Ben Walton
2009-10-09 6:53 ` Junio C Hamano [this message]
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=7v1vld5a93.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bebarino@gmail.com \
--cc=bwalton@artsci.utoronto.ca \
--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).