From: Sergey Organov <sorganov@gmail.com>
To: Johannes Altmanninger <aclopte@gmail.com>
Cc: git@vger.kernel.org, sandals@crustytoothpaste.net, solly.ucko@gmail.com
Subject: Re: rebase -i: quick/inline reword
Date: Sun, 16 Aug 2020 15:21:29 +0300 [thread overview]
Message-ID: <87mu2upyra.fsf@osv.gnss.ru> (raw)
In-Reply-To: <20200816001401.1144752-1-aclopte@gmail.com> (Johannes Altmanninger's message of "Sun, 16 Aug 2020 02:14:01 +0200")
Johannes Altmanninger <aclopte@gmail.com> writes:
>> > !f() { GIT_SEQUENCE_EDITOR=true git rebase -i --autosquash "$@"; };f
>>
>> These are very good and useful features indeed, and they are examples of
>> batch processing that is very handy for automation, but lacks
>> interactivity. What I rather have in mind is being able to put all the
>> messages /simultaneously/ into my favorite text editor and edit them
>> more or less freely till I'm satisfied, then "commit" the overall result
>> by passing it back to git. Essentially "git rebase -i" on steroids.
>
> git-revise is a third-party tool that can do this
>
> https://git-revise.readthedocs.io/en/latest/
>
> For example, "git revise -ie" allows you to edit all commit messages in
> @{u}..HEAD in a single buffer.
Yeah, exactly what is needed! And there are packages for it both in
Debian and Ubuntu, double win! Thanks for sharing!
-- Sergey
prev parent reply other threads:[~2020-08-16 12:21 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
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 [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=87mu2upyra.fsf@osv.gnss.ru \
--to=sorganov@gmail.com \
--cc=aclopte@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.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.