Re: More builtin git-am issues..

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

 



Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> writes:

> but the failing cases have a comment by Andrew:
>
>     [akpm@xxxxxxxxxxxxxxxxxxxx: coding-style fixes]
>     Signed-off-by: Tang Chen <tangchen@xxxxxxxxxxxxxx>
>     Cc: Xishi Qiu <qiuxishi@xxxxxxxxxx>
>     Cc: Yasuaki Ishimatsu <isimatu.yasuaki@xxxxxxxxxxxxxx>
>     Cc: Kamezawa Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx>
>     Cc: Taku Izumi <izumi.taku@xxxxxxxxxxxxxx>
>     Cc: Gu Zheng <guz.fnst@xxxxxxxxxxxxxx>
>     Cc: Naoya Horiguchi <n-horiguchi@xxxxxxxxxxxxx>
>     Cc: Vlastimil Babka <vbabka@xxxxxxx>
>     Cc: Mel Gorman <mgorman@xxxxxxxxxxxxxxxxxxx>
>     Cc: David Rientjes <rientjes@xxxxxxxxxx>
>     Cc: <stable@xxxxxxxxxxxxxxx>        [4.2.x]
>     Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
>
>     Signed-off-by: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
>
> ie that "[akpm@xxxxxxxxxxxxxxxxxxxx: coding-style fixes]" makes git am
> now decide that the previous block of text was not a sign-off block,
> so it adds an empty line before adding my sign-off. But very obviously
> it *was* a sign-off block.

Ahh, OK, scratch what I said earlier.  The user intended this to be
sign-off block, but the convention append_signoff() was taught from
very earlier days is that the sign-off block must consist of block
of text all of which look like rfc2822 "keyword: value" header lines,
and the comment thing makes it a non-conforming header.

Perhaps

    A block of text at the end of the existing text could be a
    signature block.  If all its lines that are rfc2822-like are at
    its end, then it is a sign-off block.  Otherwise it is not.

would allow the leading non-signature lines in the above example.

If the comment line (which I would say should have been separated by
a blank line from the signature block if only to make it easier to
read the whole thing) were in the middle, e.g.

>     Signed-off-by: Tang Chen <tangchen@xxxxxxxxxxxxxx>
>     Cc: Xishi Qiu <qiuxishi@xxxxxxxxxx>
>     Cc: Yasuaki Ishimatsu <isimatu.yasuaki@xxxxxxxxxxxxxx>
>     Cc: Vlastimil Babka <vbabka@xxxxxxx>
>     Cc: Mel Gorman <mgorman@xxxxxxxxxxxxxxxxxxx>
>     [akpm@xxxxxxxxxxxxxxxxxxxx: coding-style fixes]
>     Cc: David Rientjes <rientjes@xxxxxxxxxx>
>     Cc: <stable@xxxxxxxxxxxxxxx>        [4.2.x]
>     Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>

that rule would still not think this is a signature block, but at
that point, do we really want to consider such a block of text a
signature block?
--
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



[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]