Messages in this thread | | | From | Andi Kleen <> | Subject | Re: [PATCH 0/4] PM: Do not destroy/create devices while suspended (rev. 2) | Date | Sat, 12 Jan 2008 04:15:06 +0100 |
| |
> The real problem is that our current email workflow patterns don't > provide a standardized way for maintainers to tell when a new patch > submission is meant to override or replace an earlier submission (or > even a set of earlier submissions). Does anybody have some suggestions > for a good way to do this?
The versioning approach pioneered by Christoph Lameter seems to work reasonably well.
If you post a new version increase a version number and add it with "vXXX" to the Subject.
Also add a short change log between versions at the bottom; e.g. v1->v2: .... etc.
Then it is always clear what is the latest'n'greatest.
-Andi
| |