Thread (5 messages) flat view 5 messages, 4 authors, 2016-08-05

Re: [RFC/PATCH] rebase--interactive: Add "sign" command

From: Junio C Hamano <hidden>
Date: 2016-08-03 17:05:09

Johannes Schindelin [off-list ref] writes:
... my Git garden shears [*1*] (essentially, what
git rebase --interactive --preserve-merges *should* have been).
Any plan to fold it into "git rebase -i" as a new (improved) mode of
operation, by the way?
However, I could imagine that we actually want this to be more extensible.
After all, all you are doing is to introduce a new rebase -i command that
does nothing else than shelling out to a command.
Yup, I tend to agree.

Adding "sign" feature (i.e. make it pass -S to "commit [--amend]")
may be a good thing, but adding "sign" command to do so is not a
great design.

There is no inherent reason why "sign" feature implies "--no-edit",
and adding a "sign" command like this patch means that the next
command somebody else proposes will be "sign-and-reword".

We should be able to treat Signing and Rewording as two orthogonal
features, one that passes -S, and the other that refrains from
passing --no-edit.  Otherwise as the number of features grow, the
number of commands will see combinatorial growth.

Thanks.

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help