From: Junio C Hamano <gits...@pobox.com>
> Christian Couder <chrisc...@tuxfamily.org> writes:
>> +The trailers are recognized in the input message using the following
>> +* only lines that contains a ':' (colon) are considered trailers,
>> +* the trailer lines must all be next to each other,
>> +* after them it's only possible to have some lines that contain only
>> + spaces, and then a patch; the patch part is recognized using the
>> + fact that its first line starts with '---' (three minus signs),
>> +* before them there must be at least one line with only spaces.
> While I agree with Michael on the other thread that we should limit
> the syntax and start with ':' only, if you really want to allow
> random syntax like "Bug #12345" and "Acked-by= Peff", for which you
> have demonstrations in the tests in the other patch, the above rule
> should be updated to also allow prefix matches to possible set of
> keys defined by the user, so that an existing line that is produced
> by your tool, e.g. "Acked-by= Peff", can be picked up as matching
> with some token having a key "Acked-by= ". Otherwise, the input
> side of your tool is inconsistent with the output side of your own
> tool, and that will make the flexiblity of the output side useless.
I don't think that the flexibility of the output side would be
We already emit stuff like:
(cherry picked from commit f72baf07969242882128aff4c95ec8059e7fd054)
and we don't care about any input side when we do that.
So being able to emit lot of different stuff is valuable even if we
are not yet able to parse it.
For example what if people wanted cherry-pick messages written like:
Cherry picked from f72baf0796 ("do this and that", 2014-01-01)
we just cannot let them have the above if we decide that ':' has to
always be used as the separator.
We also emit stuff like "Merge commit '71260bf'" or "Merge tag
'mystuff'" or Merge branch 'dev' and we don't let people customize
this and we don't care about any input side.
And when there is a merge conflict we emit:
Of course at least for cherry-pick it would have been nice if since
the beginning we would have written something in a canonical trailer
This way we could now use "git interpret-trailers" to both emit the
above and to read it. But it is still be better to just be able to
emit it than to not be able to do anything about it.
Because if we are able to emit it with "git interpret-trailers", then
we can let people customize how it is emitted, and this might be
enough for many people. Also now those who are ok to output it using
the canonical way, could now configure that.
And this is not just for us, something like:
fixes #42 ("do this and that", 2014-01-01)
for example could be nice for both Github and human beings.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html