From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [announce] git patch database
Date: Fri, 16 Oct 2009 11:44:12 -0500 [thread overview]
Message-ID: <4AD8A2DC.2060202@codemonkey.ws> (raw)
In-Reply-To: <4AD89738.5010904@redhat.com>
Gerd Hoffmann wrote:
> Hi folks,
>
> I've setup some scripts which extract the patches from the list, sorts
> them, tries to apply them to master and tries to build them. Results
> can be checked here:
>
> http://repo.or.cz/w/qemu/pdb.git?a=heads
>
> Each patch (series) is committed to a new branch. In case something
> fails the logs are committed, just check out the most recent commit of
> a failed branch to figure what went wrong.
Basically, a qemu-next type tree. I think this is a really great idea
and I've been considering suggesting it.
Are you automatically merging branches into a single tree or do you just
keep each set of patches in their own branch?
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-10-16 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 15:54 [Qemu-devel] [announce] git patch database Gerd Hoffmann
2009-10-16 16:44 ` Anthony Liguori [this message]
2009-10-16 19:41 ` Gerd Hoffmann
2009-10-16 17:55 ` [Qemu-devel] " Måns Rullgård
2009-10-16 20:03 ` Gerd Hoffmann
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=4AD8A2DC.2060202@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kraxel@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.