From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] docs/traces Acked patches.
Date: Mon, 25 Mar 2013 16:04:00 -0400 [thread overview]
Message-ID: <20130325200400.GB652@phenom.dumpdata.com> (raw)
In-Reply-To: <5150957D02000078000C846A@nat28.tlf.novell.com>
On Mon, Mar 25, 2013 at 05:20:45PM +0000, Jan Beulich wrote:
> >>> On 25.03.13 at 17:46, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > On Mon, Mar 25, 2013 at 03:48:33PM +0000, Jan Beulich wrote:
> >> >>> On 25.03.13 at 16:37, George Dunlap <george.dunlap@eu.citrix.com> wrote:
> >> > On 25/03/13 15:13, Jan Beulich wrote:
> >> >>>>> On 25.03.13 at 15:41, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> >> >>> Please commit these patches. I can also put these on a git tree
> >> >>> (if you could create on for me on xenbits.org that is it) for a git pull.
> >> >>>
> >> >>>
> >> >>> The trace patches have been Acked-by George.
> >> >> You know what - I didn't apply them precisely because the ack
> >> >> came through only for patches 3 and 4. I just checked the
> >> >> xen-devel archives again, and that's the state of affairs right
> >> >> now too. Possibly the ack was sent to you without Cc-ing
> >> >> xen-devel, but that doesn't allow me to apply them.
> >> >
> >> > Is that because I had already Ack-ed an earlier version of the same
> >> > patches, as noted right above Konrad's S-o-B line?
> >>
> >> I must have overlooked that, partly because I expect Acked-by
> >> to be below Signed-off-by (only Reported-by goes ahead of it in
> >> my opinion, to reflect work/event flow).
> >
> > Oh, that would be a different workflow than with Linux, where
> > Acked-by has to be above the SOB.
>
> I just checked current SubmittingPatches and didn't spot any
> such rule.
Ha! You expect this to be documented ! :-)
>
> > The SOB of the last person posting it has to be at the bottom - as that
> > identifies who was the last person touching / sending from a git
> > tree.
>
> Yes - workflow based. Looking at the 3.8.1 change log (arbitrarily
> picked) I see no strict ordering either, and to me it just makes
> sense to apply the workflow principle here too (Reported ->
> Signed-off [-> {Acked|Reviewed|Tested|Signed-off}, ...].
So digging through my mail archive I found this from Ingo:
(Re: [GIT PULL] x86/mce fix (ready for 3.6 merge window)
We tend to use such an ordering of tags:
Signed-off-by: Tony Luck <tony.luck@intel.com>
Acked-by: Borislav Petkov <borislav.petkov@amd.com>
Cc: stable@kernel.org # 3.4+
I.e. Tested-by and Reported-by tags first (if any), then
author SOB, then SOB chain (if any), then Reviewed-by
and Acked-by, then stable tags, then Cc:s.
(I fix this up silently for email space patches, for Git pulls
I cannot do that.)
which would imply that the author's SOB is at the top - which is
what you pointed out. Perhaps I was thinking about this one and get the order
wrong. But I am pretty sure I saw somebody mention this the other
way around. Maybe it was Randy or Linus said it somewhere.
Anyhow, at this point I am just going to go with what you deem
the right way.
next prev parent reply other threads:[~2013-03-25 20:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 14:41 [PATCH] docs/traces Acked patches Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 01/11] trace: Use correct trace class for power management changes Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 02/11] trace: Add trace events for IRQ activities Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 03/11] trace: Add the other variant of do_block Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 04/11] trace: Add reason for NMI exit TRAP Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 05/11] docs: Document the ELF notes Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 06/11] docs: Document the ELF_FEATURES entry Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 07/11] docs: Add some extra details to the ELF note Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 08/11] docs: Document the shared structure Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 09/11] docs: Document the dom0_vga_console_info structure Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 10/11] docs: Document start_info changes in Xen 4.2 Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 11/11] docs: Document the XenBus structure Konrad Rzeszutek Wilk
2013-03-25 15:13 ` [PATCH] docs/traces Acked patches Jan Beulich
2013-03-25 15:37 ` George Dunlap
2013-03-25 15:48 ` Jan Beulich
2013-03-25 16:43 ` George Dunlap
2013-03-25 19:57 ` Konrad Rzeszutek Wilk
2013-03-25 16:46 ` Konrad Rzeszutek Wilk
2013-03-25 17:20 ` Jan Beulich
2013-03-25 20:04 ` Konrad Rzeszutek Wilk [this message]
2013-04-10 9:24 ` Ian Campbell
2013-03-26 16:28 ` Ian Jackson
2013-03-27 16:36 ` Konrad Rzeszutek Wilk
2013-03-28 16:00 ` Ian Jackson
2013-03-29 13:06 ` Konrad Rzeszutek Wilk
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=20130325200400.GB652@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=george.dunlap@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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;
as well as URLs for NNTP newsgroup(s).