Hi,
>> In the case of having 'exec' lines interspersed, the $commitcount
>> becomes a lot less useful (no comparison to editor line numbers),
>> though.
>
> Hmph, interesting. Then perhaps not filtering at all and instead
> labelling this new piece of information not "commit(s)" a better
> soluti
counting the number of instructions in the insn
sheet, so perhaps something like "($count todo items(s))" or
something?
> Onno
> 8< 8< 8< 8< 8< 8< 8< 8< 8<
That is not a scissors line, I suspect.
I didn't try running "git am" on this messag
now properly looks for '^pick ' patterns. I
hope this should do the trick under all circumstances? In the case
of having 'exec' lines interspersed, the $commitcount becomes a lot
less useful (no comparison to editor line numbers), though.
Cheers,
Onno
8< 8< 8< 8< 8
I see nobody commented on this, which probably fell into cracks.
Even though I am personally not very interested, I obviously am not
the only user of Git, and there may be others who are interested in
a change like this.
Onno Kortmann writes:
> Hi again,
>
> oops, I realized that my MUA mangled
Hi again,
oops, I realized that my MUA mangled the patch, even though it
shouldn't. Here it is again, with a bit more description.
---
During 'rebase -i', one wrong edit in a long rebase session might
inadvertently drop commits. This change shows the total number of
commits in the comments below
During 'rebase -i', a wrong edit command might inadvertently drop
commits. This change shows the total number of commits in the comments below
the commit list. After a rebase edit, this number can be quickly compared to
the line number of the last commit in the rebase TODO list.
Signed-off-by: Onn
6 matches
Mail list logo
