From: Stefan Weil <sw@weilnetz.de>
To: Markus Armbruster <armbru@redhat.com>, Michael Tokarev <mjt@tls.msk.ru>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Ákos Kovács" <akoskovacs@gmx.com>,
"QEMU Trivial" <qemu-trivial@nongnu.org>,
"QEMU Developer" <qemu-devel@nongnu.org>,
qemu-stable@nongnu.org, "Ozan Çag(layan" <ozancag@gmail.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.4] Update language files for QEMU 2.4.0
Date: Mon, 07 Sep 2015 19:07:24 +0200 [thread overview]
Message-ID: <55EDC44C.5080200@weilnetz.de> (raw)
In-Reply-To: <87lhciigg0.fsf@blackfin.pond.sub.org>
Am 07.09.2015 um 14:04 schrieb Markus Armbruster:
> Michael Tokarev <mjt@tls.msk.ru> writes:
>
>> 07.09.2015 09:34, Markus Armbruster wrote:
>>> Michael Tokarev <mjt@tls.msk.ru> writes:
>>>
>>>> Applied to -trivial-patches, unfortunately not for 2.4 but at least
>>>> for 2.5 :)
>>>
>>> Should we add "Cc: qemu-stable@nongnu.org" to the commit message?
>>
>> I don't think it is worth applying to stable. YMMV ofcourse :)
>
> Perhaps the stable maintainer (cc'ed) has an opinion.
>
Adding qemu-stable@nongnu.org to the cc list does not harm -
it still can be discussed whether a patch is needed or not.
In this case I think it is not needed because it is only
a patch which makes work of developers a little bit easier:
You won't get modified *.po files after a "make install".
I assume that there are much more developers compiling
and testing git master than there are for any stable release.
People building a stable version from sources without git
usually won't notice that *.po files changed.
The situation would be different if we had *.po files
with more complete translations. Then adding those files
to a stable version might be more useful.
Stefan
prev parent reply other threads:[~2015-09-07 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 5:46 [Qemu-devel] [PATCH for-2.4] Update language files for QEMU 2.4.0 Stefan Weil
2015-09-06 10:25 ` Michael Tokarev
2015-09-07 6:34 ` Markus Armbruster
2015-09-07 9:49 ` Michael Tokarev
2015-09-07 12:04 ` Markus Armbruster
2015-09-07 17:07 ` Stefan Weil [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=55EDC44C.5080200@weilnetz.de \
--to=sw@weilnetz.de \
--cc=akoskovacs@gmx.com \
--cc=armbru@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=ozancag@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=qemu-trivial@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).