Re: [PATCH] rebase -i: allow a comment after a "break" command

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hey Phillip,

Thanks for looking into this! Much appreciated!

@@ -869,7 +869,9 @@ the files and/or the commit message, amend the commit, and continue rebasing. To interrupt the rebase (just like an "edit" command would do, but without -cherry-picking any commit first), use the "break" command. +cherry-picking any commit first), use the "break" command. A "break" +command may be followed by a comment beginning with `#` followed by a +space.
Any technical reason for this? Traditionally, anything goes after a comment marker, so why be exceptional here?


Thanks,

Olliver

If you just want to edit the commit message for a commit, replace the
  command "pick" with the command "reword".
diff <https://lore.kernel.org/git/pull.1460.git.1673519809510.gitgitgadget@xxxxxxxxx/#iZ31sequencer.c> --git a/sequencer.c b/sequencer.c index bcb662e23be..c66f382dfbc 100644 --- a/sequencer.c +++ b/sequencer.c




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux