From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Fam Zheng" <fam@euphon.net>, "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] docker: Use a stable snapshot for Debian Sid
Date: Thu, 20 Dec 2018 12:20:13 +0100 [thread overview]
Message-ID: <2d4a6ad2-46d8-ca16-1bf4-10ee479fa185@redhat.com> (raw)
In-Reply-To: <CAK1Eb9mWQHXY_UEfbvFvtLvM7W3vBboEQZg-mH3-J4YRodziGg@mail.gmail.com>
Hi Fam,
On 11/2/18 8:24 AM, Fam Zheng wrote:
> On Fri, Nov 2, 2018 at 3:20 PM Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
>>
>> Hi Fam,
>>
>> Thanks for picking this.
>>
>> On Fri, Nov 2, 2018 at 7:48 AM Fam Zheng <famz@redhat.com> wrote:
>>> On Thu, 11/01 19:37, Philippe Mathieu-Daudé wrote:
>>>> The Debian Sid repository is not garanteed to be stable, as his
>>>> 'unstable' name suggest :)
>>
>> There is an error in "my be" -> "might be"...
>> Do you mind to update the comment:
>>
>>>> To allow quick testing, packages are pushed various time a day,
>>>> which my be annoying when trying to use it for stable development
>>>> (which is not recommended, but Sid provides edge packages we use
>>>> for testing).
>>
>> By:
>>
>> To allow quick testing, Debian maintainers might push packages
>> various time a day. Sometime package dependencies might break,
>> which is annoying when using this repository for stable development
>> (which is not recommended, but Sid provides edge packages we use
>> for testing).
>
> Sure, updated in my queue.
It seems your queue never hit master...
next prev parent reply other threads:[~2018-12-20 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 18:37 [Qemu-devel] [PATCH] docker: Use a stable snapshot for Debian Sid Philippe Mathieu-Daudé
2018-11-02 6:48 ` Fam Zheng
2018-11-02 7:20 ` Philippe Mathieu-Daudé
2018-11-02 7:24 ` Fam Zheng
2018-12-20 11:20 ` Philippe Mathieu-Daudé [this message]
2019-01-02 1:22 ` Fam Zheng
2019-01-10 16:16 ` Alex Bennée
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=2d4a6ad2-46d8-ca16-1bf4-10ee479fa185@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--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).