qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: stable-0.12 versus master branching?
Date: Sun, 20 Dec 2009 08:35:53 -0600	[thread overview]
Message-ID: <4B2E3649.30803@codemonkey.ws> (raw)
In-Reply-To: <20091220114812.GA15588@redhat.com>

Michael S. Tsirkin wrote:
> I am really confused wrt stable 0.12 branching policy.
> For example I see this, in master:
>
> 	commit d587e0787153f0224a6140c5015609963ceaabfb
> 	Author: Anthony Liguori <aliguori@us.ibm.com>
> 	Date:   Mon Dec 14 11:36:53 2009 -0600
>
> 	    Revert "pci: interrupt disable bit support"
>
> 	    This reverts commit 0ea5709a32085f7d14901a09d12bd35f9b267607.
>
> 	    Per discussion with Michael Tsirkin, this is too risky for 0.12
>
> 	    Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
>
> (this was cherry-picked in stable-0.12 as well).
> From the comment, this revert makes sense for stable-0.12
> but not for master.  Is this an attempt to keep stable and master
> as close as possible? I expected master development to proceed while
> stable-0.12 would get just bugfixes. No?
>   

It was a mistake.  I've already got it recommitted in master.  Just need 
to push.

Regards,

Anthony Liguori

> Thanks,
>
>   

  reply	other threads:[~2009-12-20 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-20 11:48 [Qemu-devel] stable-0.12 versus master branching? Michael S. Tsirkin
2009-12-20 14:35 ` Anthony Liguori [this message]
2009-12-21 16:24   ` [Qemu-devel] " Michael S. Tsirkin

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=4B2E3649.30803@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=mst@redhat.com \
    --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).