William Clifford <[email protected]> writes: > A couple of examples: > > - `git config sequence.format "%<(12,trunc)%ae %s"` > - `git config sequence.format "%s <%aN %aE>"` > - `git config sequence.format "%s%n%%n%b"` > ... I'm unsure what would happen if I tried to rebase with the > third style unedited or uncommented.
It should be simply forbidden. The body part may have a line that is similar enough (i.e. starting with one of the command words and then a hexadecimal string) to confuse the sequencing machinery. Other than that safety issue, I am not fundamentally opposed to the idea. As to the implementation in 1/2, your unconditional use of ">%h" is wrong (you would end up including the commits from the left side). Use '%m' instead of a hardcoded '>', perhaps? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
