From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: patch tracking tools (was Re: Maintainer abuse)
Date: Fri, 19 Dec 2014 12:30:21 +0100 [thread overview]
Message-ID: <54940C4D.6010405@redhat.com> (raw)
In-Reply-To: <20141218132505.GB21344@fam-t430.nay.redhat.com>
On 18/12/2014 14:25, Fam Zheng wrote:
> > One thing that makes automation a bit easier for QEMU is that it does
> > not have a merge window; while we do have a central committer that takes
> > pull requests, the phases are a bit more traditional (2 month
> > development, 2 weeks preparation for freeze, 1 month feature freeze).
> > For Linux it would be more important for the tool to know which patches
> > are for which tree, possibly based on the destination mailing lists.
>
> Things can be complicated, for example patch series dependencies. It's a
> question to think about whether we need it to be complete or want to keep it
> simple.
I think we want to keep it simple. Patch series dependencies complicate
the job for the maintainer too.
Andrea Arcangeli reminded me later of the obvious: for Linux such a tool
could simply use the linux-next tree as a base.
Paolo
next prev parent reply other threads:[~2014-12-19 11:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 23:24 Maintainer abuse Thomas Gleixner
2014-12-12 23:43 ` Borislav Petkov
2014-12-13 13:52 ` One Thousand Gnomes
2014-12-13 17:46 ` Borislav Petkov
2014-12-15 11:15 ` Thomas Gleixner
2014-12-16 2:47 ` Brian Norris
2014-12-18 10:14 ` patch tracking tools (was Re: Maintainer abuse) Paolo Bonzini
2014-12-18 13:25 ` Fam Zheng
2014-12-19 11:30 ` Paolo Bonzini [this message]
2014-12-16 8:06 ` Maintainer abuse Benjamin Herrenschmidt
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=54940C4D.6010405@redhat.com \
--to=pbonzini@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=famz@redhat.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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