From: Anthony Liguori <anthony@codemonkey.ws>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [FYI] Testing new patch management scripts...
Date: Fri, 04 Jan 2013 21:05:28 -0600 [thread overview]
Message-ID: <871ue0s51j.fsf@codemonkey.ws> (raw)
In-Reply-To: <50E7434E.5000305@suse.de>
Andreas Färber <afaerber@suse.de> writes:
> Hi,
>
> Am 02.01.2013 19:07, schrieb Anthony Liguori:
>> 2) Patches that no longer apply via git am --3way will receive a
>> notification.
>
> Isn't Nacked-by too strong of a notification for a mere technical need
> for a rebase (compared to a rejection of its concept/approach)?
Yeah, I need some sort of tag though for tracking purposes.. Maybe
Rejected-by...
>
> Also, since quite a few of such messages have been appearing on the list
> already, might it make sense to shorten the message and rather link to
> some qemu.org Wiki page to spare subscribers' mailboxes?
I'm focusing at the moment on getting the code in shape to release. We
can tweak the text bits over time. Patches will only send one mail
per-thread so it's unlikely that it will ever cause a space problem even
in the stingiest of corporate mailbox quotas :-)
Regards,
Anthony Liguori
>
> Regards,
> Andreas
>
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-01-05 3:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 18:07 [Qemu-devel] [FYI] Testing new patch management scripts Anthony Liguori
2013-01-04 17:01 ` Stefan Hajnoczi
2013-01-04 20:58 ` Blue Swirl
2013-01-04 21:00 ` Daniel P. Berrange
2013-01-04 21:02 ` Andreas Färber
2013-01-05 3:05 ` Anthony Liguori [this message]
2013-01-06 17:58 ` Andreas Färber
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=871ue0s51j.fsf@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=afaerber@suse.de \
--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).