Andy Parkins <andyparkins@xxxxxxxxx> writes:
> Finding the "---" separator between diff and log message could at least
> rely on finding "---" alone on a line so that "--- something else"
> wouldn't trigger the end of log?
>
> I assume this is too simple?
>
> diff --git a/builtin-mailinfo.c b/builtin-mailinfo.c
> index 766a37e..4e0795a 100644
> --- a/builtin-mailinfo.c
> +++ b/builtin-mailinfo.c
> @@ -670,7 +670,7 @@ static int handle_commit_msg(int *seen)
> return 0;
> do {
> if (!memcmp("diff -", line, 6) ||
> - !memcmp("---", line, 3) ||
> + !memcmp("---\n", line, 4) ||
> !memcmp("Index: ", line, 7))
> break;
> if ((multipart_boundary[0] && is_multipart_boundary(line))) {
I think that would make us reject patches that we currently
accept. Today, you can submit a patch created this way:
$ cp Makefile Makefile.orig
$ edit Makefile
$ cat body-of-message
$ echo "Signed-off-by: $me"
$ diff -u Makefile.orig Makefile
The first line of the diff part would be "--- Makefile.orig"
(and the second one begins with "+++ Makefile").
I do not think I've asked Linus about how he originally came up
with "three dashes at the beginning of line" convention in the
kernel circle, but my guess always have been that it would
automatically allow us to accept patches prepared like this.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html