linux-kernel - Re: patch tracking tools (was Re: Maintainer abuse)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <54940C4D.6010405@redhat.com>
Date:	Fri, 19 Dec 2014 12:30:21 +0100
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	Fam Zheng <famz@...hat.com>
CC:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	Borislav Petkov <bp@...en8.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Stefan Hajnoczi <stefanha@...hat.com>
Subject: Re: patch tracking tools (was Re: Maintainer abuse)



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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/