From: Sergey Organov <sorganov@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Solomon Ucko <solly.ucko@gmail.com>,
git@vger.kernel.org
Subject: Re: rebase -i: quick/inline reword
Date: Thu, 07 May 2020 15:17:18 +0300 [thread overview]
Message-ID: <87zhakgcs1.fsf@osv.gnss.ru> (raw)
In-Reply-To: <20200507114630.GC3027470@coredump.intra.peff.net> (Jeff King's message of "Thu, 7 May 2020 07:46:30 -0400")
Jeff King <peff@peff.net> writes:
> On Wed, May 06, 2020 at 09:52:19PM -0700, Junio C Hamano wrote:
>
>> Solomon Ucko <solly.ucko@gmail.com> writes:
>>
>> > ... It would be much easier
>> > if there were a mode where any changes to the commit titles in the list
>> > modified the commits' titles. Maybe `git rebase -i --reword`?
>> >
>> > Any thoughts, suggestions, questions, etc.?
>>
>> It is probably a bad idea, as it encourages a single-liner commit
>> message without any body.
>
> There is another legitimate use (or at least one I have wished for many
> times): when manipulating the todo list in my editor to choose patches
> for editing, I sometimes notice a typo in the title and correct it. And
> of course that does no good, and I get annoyed. You'd think I would have
> learned after all these years, but I continue to make the same mistake.
> ;)
>
> I've often wished that changes there would be quietly persisted.
That's exactly my case as well.
-- Sergey
next prev parent reply other threads:[~2020-05-07 12:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 4:27 rebase -i: quick/inline reword Solomon Ucko
2020-05-07 4:52 ` Junio C Hamano
2020-05-07 11:46 ` Jeff King
2020-05-07 12:17 ` Sergey Organov [this message]
2020-05-07 14:01 ` Solomon Ucko
2020-05-07 10:49 ` Sergey Organov
2020-05-08 0:05 ` brian m. carlson
2020-05-08 21:14 ` Sergey Organov
2020-08-16 0:14 ` Johannes Altmanninger
2020-08-16 5:36 ` Junio C Hamano
2020-08-16 12:24 ` Sergey Organov
2020-08-16 16:55 ` Junio C Hamano
2020-08-16 12:21 ` Sergey Organov
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=87zhakgcs1.fsf@osv.gnss.ru \
--to=sorganov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=solly.ucko@gmail.com \
/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.