From: Nicolas Morey-Chaisemartin <nicolas@morey-chaisemartin.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: sequencer status
Date: Wed, 23 Aug 2017 10:10:49 +0200 [thread overview]
Message-ID: <8e25c42f-80f2-e0d4-38e4-b4fe9c8074e0@morey-chaisemartin.com> (raw)
Hi,
I've created a small tool to display the current sequencer status.
It mimics what Magit does to display what was done and what is left to do.
As someone who often rebase large series of patches (also works with am, revert, cherry-pick), I really needed the feature and use this daily.
It's available here:
https://github.com/nmorey/git-sequencer-status
SUSE and Fedora packages are available here:
https://build.opensuse.org/package/show/home:NMoreyChaisemartin:git-tools/git-sequencer-status
It's not necessary very robust yet. Most of the time I use simple rebase so there are a lot of untested corner cases.
Here is an example output:
$ sequencer-status
# Interactive rebase: master onto rebase_conflict
exec true
pick e54d993 Fourth commit
exec true
*pick b064629 Third commit
exec true
pick 174c933 Second commit
onto 773cb23 Alternate second
Two questions:
- Could this be a candidate for contrib/ ?
- Would it be interesting to add the relevant code to sequencer.c so that all sequencer based commands could have a --status option ?
Nicolas
next reply other threads:[~2017-08-23 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 8:10 Nicolas Morey-Chaisemartin [this message]
2017-08-23 16:40 ` sequencer status Christian Couder
2017-08-24 8:07 ` Nicolas Morey-Chaisemartin
2017-08-24 9:43 ` Matthieu Moy
2017-08-24 10:12 ` Nicolas Morey-Chaisemartin
2017-08-23 17:57 ` Junio C Hamano
2017-08-24 8:16 ` Nicolas Morey-Chaisemartin
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=8e25c42f-80f2-e0d4-38e4-b4fe9c8074e0@morey-chaisemartin.com \
--to=nicolas@morey-chaisemartin.com \
--cc=git@vger.kernel.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 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.