From: Andi Kleen <ak@suse.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
rjw@sisk.pl, linux-pm@lists.linux-foundation.org,
linux-acpi@vger.kernel.org, lenb@kernel.org,
linux-kernel@vger.kernel.org, pavel@suse.cz, mingo@elte.hu,
tglx@linutronix.de
Subject: Re: [PATCH 0/4] PM: Do not destroy/create devices while suspended (rev. 2)
Date: Sat, 12 Jan 2008 04:15:06 +0100 [thread overview]
Message-ID: <200801120415.07176.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0801112208030.21411-100000@netrider.rowland.org>
> 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
next prev parent reply other threads:[~2008-01-12 3:15 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 23:32 [PATCH 0/4] PM: Do not destroy/create devices while suspended (rev. 2) Rafael J. Wysocki
2008-01-01 23:34 ` [PATCH 1/4] PM: Introduce destroy_suspended_device() Rafael J. Wysocki
2008-01-02 13:33 ` Rafael J. Wysocki
2008-01-02 16:41 ` Alan Stern
2008-01-02 16:50 ` Rafael J. Wysocki
2008-01-04 22:05 ` Rafael J. Wysocki
2008-01-04 23:29 ` [RFC][PATCH] PM: Acquire device locks on suspend (was: Re: [PATCH 1/4] PM: Introduce destroy_suspended_device()) Rafael J. Wysocki
2008-01-05 3:11 ` [PATCH 1/4] PM: Introduce destroy_suspended_device() Alan Stern
2008-01-05 11:55 ` Rafael J. Wysocki
2008-01-01 23:40 ` [PATCH 2/4] PM: Do not destroy/create devices while suspended in msr.c (rev. 2) Rafael J. Wysocki
2008-01-01 23:40 ` [PATCH 3/4] PM: Do not destroy/create devices while suspended in mce_64.c Rafael J. Wysocki
2008-01-01 23:42 ` [PATCH 4/4] PM: Do not destroy/create devices while suspended in cpuid.c Rafael J. Wysocki
2008-01-02 10:52 ` [PATCH 0/4] PM: Do not destroy/create devices while suspended (rev. 2) Ingo Molnar
2008-01-02 12:56 ` Rafael J. Wysocki
2008-01-02 13:15 ` Ingo Molnar
2008-01-02 13:28 ` Rafael J. Wysocki
2008-01-03 10:56 ` Pavel Machek
2008-01-02 14:55 ` Kay Sievers
2008-01-02 16:01 ` Ingo Molnar
2008-01-02 17:54 ` David Brownell
2008-01-02 18:05 ` Alessandro Zummo
2008-01-02 18:12 ` David Brownell
2008-01-02 18:34 ` Alessandro Zummo
2008-01-02 20:14 ` Ingo Molnar
2008-01-02 20:29 ` David Brownell
2008-01-02 17:26 ` David Brownell
2008-01-02 20:17 ` Ingo Molnar
2008-01-12 0:46 ` Andrew Morton
2008-01-12 0:49 ` Andrew Morton
2008-01-12 0:56 ` Greg KH
2008-01-12 3:11 ` Alan Stern
2008-01-12 3:15 ` Andi Kleen [this message]
2008-01-12 3:21 ` Andrew Morton
2008-01-12 4:29 ` Greg KH
2008-01-12 11:25 ` Rafael J. Wysocki
2008-01-12 11:20 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200801120415.07176.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox