From: Tim Mazid <timmazid@hotmail.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Ramkumar Ramachandra <artagnon@gmail.com>
Subject: Re: [PATCH] rebase: learn --discard subcommand
Date: Mon, 30 May 2011 15:14:35 +1000 [thread overview]
Message-ID: <20110530051434.GA3723@Imperial-SD-Longsword> (raw)
In-Reply-To: <4DE32138.4050104@alum.mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
On Mon, May 30, 2011 at 06:46:48AM +0200, Michael Haggerty wrote:
> On 05/29/2011 01:08 AM, Jonathan Nieder wrote:
> > Agh, "git rebase --abort --keep-head" feels a little too long to be
> > memorable. Still, hope that helps.
>
> It seems like the distinction is analogous to "git reset --soft", so maybe
>
> git rebase --abort --soft
Well, the only problem with that is the "--soft" option refers to the
"reset" command given to git, whereas in your proposed syntax, the
"--soft" option refers to the _other_ option, "--abort".
This may seem a little nit-picky, but such a difference could lead to
confusion. Perhaps "--soft-abort" or "--soft-abort" would be better? A
single option to the "git rebase" command rather than a "sub-option"
given to another option.
It just seems to me that all the git commands work this way; "git
command --options-to-command". An option to another option just seems
too confusing.
Of course, there's the floodgate problem; once you have options to
options, are you going to have options to options to options, ad
infinitum?
--
Tim
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-05-30 5:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 2:58 [PATCH] rebase: learn --discard subcommand Martin von Zweigbergk
2011-05-28 13:15 ` Ramkumar Ramachandra
2011-05-29 12:50 ` Martin von Zweigbergk
2011-05-28 18:51 ` Junio C Hamano
2011-05-28 20:26 ` Tim Mazid
2011-05-28 22:50 ` Jonathan Nieder
2011-05-29 13:14 ` Martin von Zweigbergk
2011-05-29 13:41 ` Jakub Narebski
2011-05-30 4:50 ` Michael Haggerty
2011-05-28 23:08 ` Jonathan Nieder
2011-05-29 9:30 ` Tim Mazid
2011-05-29 17:28 ` Martin von Zweigbergk
2011-05-29 18:58 ` Jonathan Nieder
2011-05-30 4:46 ` Michael Haggerty
2011-05-30 5:14 ` Tim Mazid [this message]
2011-05-30 8:44 ` Michael Haggerty
2011-05-30 5:01 ` Miles Bader
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=20110530051434.GA3723@Imperial-SD-Longsword \
--to=timmazid@hotmail.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=martin.von.zweigbergk@gmail.com \
--cc=mhagger@alum.mit.edu \
/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).