Re:Show HN: Sedy, a GitHub Bot Bringing Linux Sed to Code Re...
by Kmaschta on Tuesday February 28, 2017 @10:07AM
(#13754214)
What about a command s/[search]/[replace]/a for "--amend"?
Re:Show HN: Sedy, a GitHub Bot Bringing Linux Sed to Code Re...
by LukeShu on Tuesday February 28, 2017 @10:10AM
(#13754245)
That could win me over! I'm not sure what the appropriate answer is to "who should it put in the committer line?" (especially if author and committer are already different), but that's not a huge problem, I don't think.
Re:Show HN: Sedy, a GitHub Bot Bringing Linux Sed to Code Re...
by pavel_lishin on Tuesday February 28, 2017 @01:21PM
(#13756179)
It would be a problem for me - suddenly, my local branch and the Github branch are no longer in sync, and I have to untangle this mess before continuing development. (And if I don't notice that Sedy is changing the revision history, and only realize it when I've made a couple of commits and try to push...)
Re:Show HN: Sedy, a GitHub Bot Bringing Linux Sed to Code Re...
by hamandcheese on Tuesday February 28, 2017 @11:16AM
(#13754813)
You could do an interactive rebase and make all the Sedy commits fixups.
For those simple types of changes, I like to amend the original commit, rather than make a new one. Of course, I come from using `git send-email` to send patches to a mailing list, where you are expected to send "[PATCH v2]" after you get feedback.