linux-kernel - Re: linux-next: Tree for Sep 25

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131003133051.GB25934@localhost>
Date:	Thu, 3 Oct 2013 21:30:51 +0800
From:	Fengguang Wu <fengguang.wu@...el.com>
To:	Joe Perches <joe@...ches.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: Tree for Sep 25

On Wed, Sep 25, 2013 at 05:47:28PM -0700, Joe Perches wrote:
> On Wed, 2013-09-25 at 14:43 +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Heads up: I will be having a 3 week break leading up to the kernel
> > summit.  This means that next-20130927 (next Friday) will be the last
> > linux-next release until next-20131028 (or maybe 29).  I presume that
> > Linus will be up to v3.12-rc7 by then and -rc7 is often the last before
> > a release ... Please plan accordingly.
> 
> Hi Stephen.
> 
> Maybe this is a good time for an experiment.
> 
> Perhaps it would be interesting if you still had a script
> running every workday and pushed out the result tree without
> trying to do any patch conflict resolution yourself.
> 
> Maybe notify the owners of the trees that conflict and let
> them work out whatever resolutions that are necessary.
> 
> I think FengGuang's robot can supply most all the details
> necessary and maybe you can do a lot less work in the future.

It's a good idea, unfortunately Stephen has already went to vocation.
I could try the auto merge and merge-failure reports and hand the
script over to Stephen when he is back. However the merge conflicts
will have to be handled by the relevant developer/maintainers.

Thanks,
Fengguang
--
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/