From: Christian Couder <christian.couder@gmail.com>
To: Nicolas Morey-Chaisemartin <nicolas@morey-chaisemartin.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: sequencer status
Date: Wed, 23 Aug 2017 18:40:31 +0200 [thread overview]
Message-ID: <CAP8UFD035niTUQTe73RSTE+3u6WX11UpxoqCSrfVP1Qs-fF0gg@mail.gmail.com> (raw)
In-Reply-To: <8e25c42f-80f2-e0d4-38e4-b4fe9c8074e0@morey-chaisemartin.com>
Hi,
On Wed, Aug 23, 2017 at 10:10 AM, Nicolas Morey-Chaisemartin
<nicolas@morey-chaisemartin.com> wrote:
> 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.
Yeah, many people use the interactive rebase a lot so I think it could
be very interesting.
> 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
It is displaying the steps that have already been performed, right?
I wonder if people might want more about the current step (but maybe
that belongs to `git status`) or perhaps the not yet performed states
(and maybe even a way to edit the todo list?)
> Two questions:
> - Could this be a candidate for contrib/ ?
It seems to me that these days we don't often add new tools to contrib/.
> - Would it be interesting to add the relevant code to sequencer.c so that all sequencer based commands could have a --status option ?
Yeah, it's probably better if it's integrated in git, either as a
--status option in some commands, or perhaps as an option of `git
status`.
Thanks,
Christian.
next prev parent reply other threads:[~2017-08-23 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 8:10 sequencer status Nicolas Morey-Chaisemartin
2017-08-23 16:40 ` Christian Couder [this message]
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=CAP8UFD035niTUQTe73RSTE+3u6WX11UpxoqCSrfVP1Qs-fF0gg@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=nicolas@morey-chaisemartin.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 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).