From: liam Beguin <liambeguin@gmail.com>
To: Jacob Keller <jacob.keller@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Cc: Git mailing list <git@vger.kernel.org>,
Jhannes.Schindelin@gmx.de, Jeff King <peff@peff.net>
Subject: Re: [PATCH v2] rebase -i: add config to abbreviate command-names
Date: Tue, 25 Apr 2017 19:34:26 -0400 [thread overview]
Message-ID: <1493163266.29673.29.camel@gmail.com> (raw)
In-Reply-To: <CA+P7+xrXyguugTETd_C-JXDSZ5zHUC3d_1cU4CuiaJjAqWQ=RA@mail.gmail.com>
Hi Jake,
On Tue, 2017-04-25 at 01:29 -0700, Jacob Keller wrote:
> On Mon, Apr 24, 2017 at 11:29 PM, Junio C Hamano <gitster@pobox.com> wrote:
> > Personally I am happy with the beginning of each instruction line
> > aligned, so from that point of view, this patch is a mild Meh to me,
> > even though I do a fair amount of "rebase -i" myself. But obviously
> > I am not the only user of Git you need to please, so...
>
> I would instead justify this as making it easier to change the action,
> since you only need to rewrite a single letter, which at least in vim
> takes "r<letter>" to change the action, vs slightly more keystrokes
> such as "ct <letter" or otherwise.
It's another reason that motivated the change but I didn't think the
vim shortcuts would justify the patch. Since you pointed it out,
I'll probably add it.
>
> Also, if you change the default commit hash length, it becomes long
> enough to cover most commits and you see all commits at say 12 digits
> commit hash and everything is nicely aligned.
>
> Thanks,
> Jake
Thanks,
Liam
next prev parent reply other threads:[~2017-04-25 23:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 3:23 [PATCH] rebase -i: add config to abbreviate command name Liam Beguin
2017-04-24 10:26 ` Johannes Schindelin
2017-04-24 11:04 ` liam BEGUIN
2017-04-25 2:57 ` liam BEGUIN
2017-04-25 19:45 ` Johannes Schindelin
2017-04-25 22:58 ` liam BEGUIN
2017-04-24 12:29 ` Jeff King
2017-04-25 4:37 ` [PATCH v2] rebase -i: add config to abbreviate command-names Liam Beguin
2017-04-25 6:29 ` Junio C Hamano
2017-04-25 8:29 ` Jacob Keller
2017-04-25 23:34 ` liam Beguin [this message]
2017-04-26 2:09 ` Junio C Hamano
2017-04-25 9:57 ` Andreas Schwab
2017-04-25 13:59 ` Mike Rappazzo
2017-04-25 10:34 ` Philip Oakley
2017-04-25 4:43 ` Liam Beguin
2017-04-25 9:53 ` Andreas Schwab
2017-04-25 21:23 ` Johannes Schindelin
2017-04-25 22:56 ` liam BEGUIN
2017-04-25 20:08 ` Johannes Schindelin
2017-04-26 0:13 ` liam Beguin
2017-04-26 1:47 ` Jeff King
2017-04-26 3:59 ` Junio C Hamano
2017-04-26 9:25 ` Johannes Schindelin
2017-04-27 0:37 ` Junio C Hamano
2017-04-26 9:28 ` Johannes Schindelin
2017-04-26 15:24 ` Ævar Arnfjörð Bjarmason
2017-04-27 1:20 ` liam Beguin
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=1493163266.29673.29.camel@gmail.com \
--to=liambeguin@gmail.com \
--cc=Jhannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.keller@gmail.com \
--cc=peff@peff.net \
/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).