From: Junio C Hamano <gitster@pobox.com>
To: "Kelvie Wong" <kelvie@ieee.org>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] Add an "-i" option to git-reset, to confirm a reset.
Date: Sun, 16 Dec 2007 12:09:40 -0800 [thread overview]
Message-ID: <7vwsrejta3.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <94ccbe710712151946u22f02a8fkbc3c4cbc96ee22f5@mail.gmail.com> (Kelvie Wong's message of "Sat, 15 Dec 2007 19:46:10 -0800")
"Kelvie Wong" <kelvie@ieee.org> writes:
> On Dec 15, 2007 7:35 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> ..
>> I am slightly negative on this patch. Not only do I think that it is both
>> easier and more natural to run diff/status/an-alias to see what a reset
>> would do, but the patch only handles the index_file part (missing the --
>> <file> part AFAICT).
I am in principle very negative on additional option that does the same
thing as what the users on odd occasions can run a separate command
themselves to achieve, and I think "reset -i" falls into that category.
And I am negative on this "-i" not just because I think that would be
only in "odd occasions" (i.e. rare), but because I think it would not
help much. Either you are sure about resetting, in which case you would
not even use "-i" option (and not get this safety), or you are unsure,
in which case you can do "git status" or whatever commands that are
already available.
> w.r.t. the style, you were referring to just the array initializers
> right? Or was there something else I did that doesn't look right?
I spotted only two classes.
+
+ /* Show the user what is about to be reset, and in more detail, if they
+ * like. */
/*
* Show the user what is about to be reset, and in more detail,
* if they like.
*/
+ if(confirm_reset) {
if (confirm_reset) {
next prev parent reply other threads:[~2007-12-16 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 3:26 [PATCH] Add an "-i" option to git-reset, to confirm a reset Kelvie Wong
2007-12-16 3:35 ` Johannes Schindelin
2007-12-16 3:46 ` Kelvie Wong
2007-12-16 20:09 ` Junio C Hamano [this message]
2007-12-16 21:26 ` Kelvie Wong
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=7vwsrejta3.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=kelvie@ieee.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).