All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Laszlo Ersek <lersek@redhat.com>,
	Ladi Prosek <lprosek@redhat.com>, Jeff Cody <jcody@redhat.com>
Subject: [Qemu-devel] ipxe for qemu maintainance
Date: Wed, 22 Feb 2017 14:42:34 +0100	[thread overview]
Message-ID: <1487770954.4687.2.camel@redhat.com> (raw)

  Hi folks,

I'd like to start maintaining qemu-specific branches in our ipxe.git
repo.  The reason for this are some problems with the upstream ipxe
maintainance:

 * The ipxe maintainer apparently is pretty busy.  Often (but not
   always) it takes weeks or even months to get patches merged upstream,
   which is bad in case we need a fix included quickly due to freeze
   deadline approaching ...
 * There is no release management whatsoever.  No stable branches,
   no release tags.  Picking up a fix upstream means rebasing to
   a snapshot which includes the fix.

So I'd like to improve that downstream with qemu branches, where we can
commit not-yet merged patches, revert broken patches and cherry-pick
bugfixes.

This is *NOT* meant to be a replacement for working with upstream to get
patches merged and bugs fixed.  But it will allow us to handle things in
a timely manner without having to depend on the upstream maintainer.
And we can be more selective about the ipxe patches we accept during
freeze.

I plan to also add qemu release tags to the repo, so you can easily
figure what is included in each qemu release.

Laszlo created a wiki page for this, naming conventions for branches and
tags are listed there too:
        http://wiki.qemu-project.org/IpxeDownstreamForQemu

Comments?

cheers,
  Gerd

PS: v2, this time with the correct qemu-devel address ...

             reply	other threads:[~2017-02-22 13:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 13:42 Gerd Hoffmann [this message]
2017-05-09 17:59 ` [Qemu-devel] ipxe for qemu maintainance Jeff Cody

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=1487770954.4687.2.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=jcody@redhat.com \
    --cc=lersek@redhat.com \
    --cc=lprosek@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.