qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v2 00/54] Kconfig conversion, excluding ARM and MIPS
Date: Thu, 7 Mar 2019 21:57:35 +0100	[thread overview]
Message-ID: <2d2db167-2b50-3c51-6739-6b72339bc90c@redhat.com> (raw)
In-Reply-To: <CAFEAcA9=eKhnL40T8nZuktoVGabq8MoGoYLiRO1fjg9dsNXLXQ@mail.gmail.com>

On 07/03/19 19:35, Peter Maydell wrote:
> On Thu, 7 Mar 2019 at 14:18, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>> The following changes since commit 1ba530a4ecba6015d52d8f392fd327cfa07bc37a:
>>
>>   Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20190304' into staging (2019-03-04 13:38:54 +0000)
>>
>> are available in the git repository at:
>>
>>
>>   git://github.com/bonzini/qemu.git tags/for-upstream-kconfig
>>
>> for you to fetch changes up to 1f749c0626f6f79cfc27fc3e6b910a6df03d3488:
>>
>>   kconfig: add documentation (2019-03-07 15:06:29 +0100)
>>
>> ----------------------------------------------------------------
>> Initial Kconfig work, excluding ARM and MIPS
> 
> This passes my build tests, but something in your workflow
> has mangled a Cc: line in one of the commit messages.
> In commit 11db78e98317e1a0c the accented character in
> Hervé Poussineau's name has been mangled and isn't correct
> UTF-8. Could you fix that up and resend, please?
> 
> PS: since the sphinx patchset just got in ahead of
> yours, Sphinx now warns:
> docs/devel/kconfig.rst: WARNING: document isn't included in any toctree
> 
> I'll send a followup patch which adds 'kconfig' to
> docs/devel/index.rst once this is merged.

I just rebased and did the change myself, which was a good idea because
I also had to use ==== headings instead of ---- for the ToC to come out
right.

Thanks for working on Sphinx!  I will dig out the Texinfo->Sphinx
patches for 4.1, as well as the small changes to kerneldoc that support
QEMU's hybrid of kerneldoc and gtkdoc.

Paolo

      reply	other threads:[~2019-03-07 20:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 14:16 [Qemu-devel] [PULL v2 00/54] Kconfig conversion, excluding ARM and MIPS Paolo Bonzini
2019-03-07 14:16 ` [Qemu-devel] [PULL v2 26/54] tpm: express dependencies with Kconfig Paolo Bonzini
2019-03-07 18:35 ` [Qemu-devel] [PULL v2 00/54] Kconfig conversion, excluding ARM and MIPS Peter Maydell
2019-03-07 20:57   ` Paolo Bonzini [this message]

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=2d2db167-2b50-3c51-6739-6b72339bc90c@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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).