From: Tyler Hicks <tyhicks@canonical.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v7 1/5] NX 1
Date: Thu, 24 Oct 2019 10:01:16 -0500 [thread overview]
Message-ID: <20191024150116.GA25053@elm> (raw)
In-Reply-To: <82b4c6b0-16cd-d37b-4107-d53ee503b4e6@redhat.com>
On 2019-10-24 16:25:00, speck for Paolo Bonzini wrote:
> On 24/10/19 16:21, speck for Tyler Hicks wrote:
> > On 2019-10-24 10:57:57, speck for Paolo Bonzini wrote:
> >> Uhm, this time I'm sure that I included the From/Subject lines, both in
> >> this series and the QEMU patch.
> >
> > In another thread, Pawan and Thomas identified an additional newline
> > that needed to be emitted from speckify-gitmail. While digging up the
> > details to pass on to you, I noticed that Thomas just uploaded
> > speck-utils-v2 that contains the change:
> >
> > https://tglx.de/~tglx/.utils/
> >
> > Sorry for stealing your thunder on the v2 announcement, Thomas. :)
>
> I see (I had written my own script though before speck-utils was a
> thing, or at least before I learnt about it, so I'll have to dig out
> that thread).
Message ID <20191021203528.GD23497@guptapadev.amr> is what you'll need
to search for.
Tyler
>
> I think I'll just send a git bundle later today.
>
> Paolo
>
>
next prev parent reply other threads:[~2019-10-24 15:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 7:34 [MODERATED] [PATCH v7 0/5] NX 0 Paolo Bonzini
2019-10-24 7:34 ` [MODERATED] [PATCH v7 1/5] NX 1 Paolo Bonzini
2019-10-24 8:57 ` [MODERATED] " Paolo Bonzini
2019-10-24 14:21 ` Tyler Hicks
2019-10-24 14:25 ` Paolo Bonzini
2019-10-24 15:01 ` Tyler Hicks [this message]
2019-10-24 7:34 ` [MODERATED] [PATCH v7 2/5] NX 2 Paolo Bonzini
2019-10-24 7:34 ` [MODERATED] [PATCH v7 3/5] NX 3 Paolo Bonzini
2019-10-24 7:34 ` [MODERATED] [PATCH v7 4/5] NX 4 Paolo Bonzini
2019-10-24 7:34 ` [MODERATED] [PATCH v7 5/5] NX 5 Paolo Bonzini
2019-10-28 12:08 ` [PATCH v7 0/5] NX 0 Thomas Gleixner
2019-10-28 16:02 ` [MODERATED] Re: ***UNCHECKED*** " Joerg Roedel
2019-10-29 8:51 ` Thomas Gleixner
2019-10-29 9:39 ` [MODERATED] Re: ***UNCHECKED*** " Joerg Roedel
2019-10-29 11:00 ` Thomas Gleixner
2019-10-29 12:31 ` [MODERATED] Re: ***UNCHECKED*** " Joerg Roedel
2019-10-29 15:35 ` Thomas Gleixner
2019-10-29 15:42 ` [MODERATED] Re: ***UNCHECKED*** " Joerg Roedel
2019-10-29 16:50 ` Paolo Bonzini
2019-10-31 21:00 ` [MODERATED] Re: ***UNCHECKED*** " Tyler Hicks
2019-10-31 22:13 ` Paolo Bonzini
2019-10-24 16:34 [MODERATED] " Paolo Bonzini
2019-10-24 16:34 ` [MODERATED] [PATCH v7 1/5] NX 1 Paolo Bonzini
2019-10-30 18:38 ` [MODERATED] " Josh Poimboeuf
2019-10-31 11:05 ` Paolo Bonzini
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=20191024150116.GA25053@elm \
--to=tyhicks@canonical.com \
--cc=speck@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;
as well as URLs for NNTP newsgroup(s).