[PATCH v2 0/3] Quieter sequencer status parsing

2019-06-27 Thread Phillip Wood via GitGitGadget
r-275/phillipwood/wip/quieter sequencer status parsing-v2 Pull-Request: https://github.com/gitgitgadget/git/pull/275 Range-diff vs v1: 1: a5bede1cf9 = 1: a5bede1cf9 sequencer: always allow tab after command name 2: ebe8a2b3a1 ! 2: c3885c0b8f sequencer: factor out todo command name parsing @@

Re: [PATCH 0/3] Wip/quieter sequencer status parsing

2019-06-25 Thread Phillip Wood
c85dc66810 Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-275%2Fphillipwood%2Fwip%2Fquieter%C2%A0sequencer%C2%A0status%C2%A0parsing-v1 Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-275/phillipwood/wip/quieter sequencer status parsing-v1 Pull-Request: https://

[PATCH 0/3] Wip/quieter sequencer status parsing

2019-06-25 Thread Phillip Wood via GitGitGadget
https://github.com/gitgitgadget/git pr-275/phillipwood/wip/quieter sequencer status parsing-v1 Pull-Request: https://github.com/gitgitgadget/git/pull/275 -- gitgitgadget

Re: sequencer status

2017-08-24 Thread Nicolas Morey-Chaisemartin
Le 24/08/2017 à 11:43, Matthieu Moy a écrit : > Christian Couder writes: > >> 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 >> (a

Re: sequencer status

2017-08-24 Thread Matthieu Moy
Christian Couder writes: > 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?) Note that

Re: sequencer status

2017-08-24 Thread Nicolas Morey-Chaisemartin
nerally a good idea or not. In any case, having such a > front-end will help third-party scripts that want to build a custom > workflow using the sequecing machinery we have. > > And in such a world, we would need "git sequencer status" command > to give us where in a larger

Re: sequencer status

2017-08-24 Thread Nicolas Morey-Chaisemartin
Le 23/08/2017 à 18:40, Christian Couder a écrit : > Hi, > > On Wed, Aug 23, 2017 at 10:10 AM, Nicolas Morey-Chaisemartin > wrote: >> Hi, >> >> I've created a small tool to display the current sequencer status. >> It mimics what Magit does to dis

Re: sequencer status

2017-08-23 Thread Junio C Hamano
un "git sequencer continue", bypassing frontends for individual commands, e.g. "git cherry-pick --continue", etc., but I do not know if that is generally a good idea or not. In any case, having such a front-end will help third-party scripts that want to build a custom workfl

Re: sequencer status

2017-08-23 Thread Christian Couder
Hi, On Wed, Aug 23, 2017 at 10:10 AM, Nicolas Morey-Chaisemartin 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

sequencer status

2017-08-23 Thread Nicolas Morey-Chaisemartin
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.