From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH] docs/traces Acked patches.
Date: Mon, 25 Mar 2013 15:37:27 +0000 [thread overview]
Message-ID: <51506F37.70600@eu.citrix.com> (raw)
In-Reply-To: <515077C402000078000C830A@nat28.tlf.novell.com>
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'm not 100% sure the normal protocol, but Konrad has been around the
block a few times; I would think that if Konrad put my Ack-by on
something, then that should have the presumption of validity --
particularly if he cc'd me (which he did) and I didn't nack it.
-George
next prev parent reply other threads:[~2013-03-25 15:37 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 [this message]
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
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=51506F37.70600@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=konrad.wilk@oracle.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).