On Sun, 2014-07-20 at 19:13 +0200, Fabian Frederick wrote:
> I was reading all those "friendly" messages around checkpatch -f lately
> and the fact that code clean-up is too noisy (?)
>
> I guess I'm not the first to think about it but why don't we use something
> like a priority field in patch subject ?
>
> Of course it would be arbitrary but maybe better than nothing ?
>
> eg
>
> [PATCH 1/1 0] Urgent bug fix
> [PATCH 1/1 1] Bug fix
> [PATCH 1/1 2] ...
> [PATCH 1/1 7] kernel-doc fix
> [PATCH 1/1 8] Code clean-up
> [PATCH 1/1 9] Trivial fix
>
> Maybe this could help some people to sort/filter/delete
>
> It's just an idea of course...
It's a good idea, but this is more a subject for
discussion on and by the list than off-list so I'm
adding LKML.
As far as I know, the only infrequently used prefixes
today are "RFC" and "trivial".
If you start to use a prefix, please use readable
text and not some numeric table index.
[RFC PATCH]
[URGENT PATCH]
[BUGFIX PATCH]
[TRIVIAL PATCH]
[CODE STYLE PATCH]
etc...
Getting people to use
git format-patch --subject-prefix="text"
will be the useful part of this challenge.
Maybe you could develop YA little helper script for
that, ideally with versioning support for repeated
patch submissions too.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
