From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Nate Studer <nate.studer@dornerworks.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.4 development update: Feature freeze has started
Date: Fri, 15 Nov 2013 10:41:40 +0100 [thread overview]
Message-ID: <1384508500.3827.6.camel@Abyss.lan> (raw)
In-Reply-To: <5285F17D02000078001036D4@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1404 bytes --]
On ven, 2013-11-15 at 09:03 +0000, Jan Beulich wrote:
> >>> On 14.11.13 at 23:20, Dario Faggioli <dario.faggioli@citrix.com> wrote:
> > It looks fine to me. Unfortunately, I double checked and I don't find
> > the actual e-mail in my inbox, so I'm saying this here: the patch at the
> > above URL can have, FWIW, my
> >
> > Reviewed-by: Dario Faggioli <dario.faggioli@citrix.com>
>
> Please, for the future, reply to the patch mail with any reviews
> or acks - relying on committers to be collecting them from unrelated
> threads is rather unreliable.
>
I know that, and I'm sorry. If you want to ignore the above because it
doesn't follow the regular procedure, feel free, I know it's my fault
and thus I'm fine dealing with the consequences.
Unfortunately, as I said, either the message with the patch did (for
some reason) not hit my inbox, or I accidentally deleted it, so I really
didn't have a message to reply to, but still I wanted to state that I
reviewed it and find it sound. I think it's the first time I do that,
and I certainly don't plan to do it again..
Anyway, sorry again for the noise.
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-11-15 9:41 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 17:18 Xen 4.4 development update: Feature freeze has started George Dunlap
2013-11-11 17:32 ` Andrew Cooper
2013-11-15 14:36 ` George Dunlap
2013-11-15 14:44 ` Jan Beulich
2013-11-15 14:48 ` Andrew Cooper
2013-11-15 14:52 ` Andrew Cooper
2013-11-11 18:03 ` Konrad Rzeszutek Wilk
2013-11-12 8:55 ` Jan Beulich
2013-11-12 12:04 ` Stefano Stabellini
2013-11-12 14:17 ` Konrad Rzeszutek Wilk
2013-11-12 9:24 ` Ian Campbell
2013-11-11 20:49 ` Boris Ostrovsky
2013-11-11 21:02 ` Ben Guthro
2013-11-12 10:54 ` David Vrabel
2013-11-12 11:09 ` Ian Campbell
2013-11-12 11:11 ` Roger Pau Monné
2013-11-15 15:37 ` George Dunlap
2013-11-15 15:51 ` Roger Pau Monné
2013-11-12 11:20 ` Wei Liu
2013-11-12 11:53 ` Fabio Fantoni
2013-11-12 12:49 ` Stefano Stabellini
2013-11-12 14:20 ` Konrad Rzeszutek Wilk
2013-11-12 14:22 ` Ian Campbell
2013-11-12 14:26 ` Wei Liu
2013-11-12 15:07 ` Konrad Rzeszutek Wilk
2013-11-12 15:16 ` Wei Liu
2013-11-15 16:11 ` George Dunlap
2013-11-15 16:28 ` George Dunlap
2013-11-19 10:47 ` Ian Campbell
2013-11-14 9:28 ` Dario Faggioli
2013-11-14 14:16 ` Nate Studer
2013-11-14 22:20 ` Dario Faggioli
2013-11-15 9:03 ` Jan Beulich
2013-11-15 9:41 ` Dario Faggioli [this message]
2013-11-15 9:00 ` Jan Beulich
2013-11-14 9:38 ` Dario Faggioli
2013-11-14 13:42 ` Elena Ufimtseva
2013-11-15 16:34 ` George Dunlap
2013-11-15 18:07 ` Dario Faggioli
2013-11-15 20:39 ` Shriram Rajagopalan
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=1384508500.3827.6.camel@Abyss.lan \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=nate.studer@dornerworks.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).