Explicitly documenting patch submission
A message that is not in the archive (sent off-list or not yet received): [email protected]
[email protected] (Linus Torvalds) wrote on 25.05.04 in <[email protected]>:
Quoted 11 lines · Albert Cahalan
Quoted 3 lines
The wordy mix-case aspect is kind of annoying, and for all that we don't get to differentiate actions.
I actually really really don't want to differentiate actions. There's really no reason to try to separate things out, and quite often the actions are mixed anyway. Besides, if they all end up having the same technical meaning ("I have the right to pass on this patch") having separate flags is just sure to confuse the process.
Quoted 6 lines
So what I want is something _really_ simple. Something that is unambigious, and cannot be confused with something else. And in particular, I want that sign-off line to be "strange" enough that there is no possibility of ever writing that line by mistake - so that it is clear that the only reason anybody would write something like "Signed-off-by:" is because it meant _that_ particular thing.
So it might be wise to add something approximately like this:
Sometimes, pieces wander from one project into another, and tracking that as well could possibly help.
MfG Kai