linux-kernel - Re: [git pull] drm for 4.3

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]

Date:	Tue, 8 Sep 2015 14:56:22 +1000
From:	Dave Airlie <airlied@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	DRI mailing list <dri-devel@...ts.freedesktop.org>
Subject: Re: [git pull] drm for 4.3

On 8 September 2015 at 14:04, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Dave,
>
> On Tue, 8 Sep 2015 13:01:21 +1000 Dave Airlie <airlied@...il.com> wrote:
>>
>> Is this to be a regular thing? because I know I'd prefer to merge
>> fixes than wait for -rc1 to be an accurate copy of linux-next.
>
> It happens when I can (almost) keep up with Linus' merge rate (often I
> can't).  It is not an issue and I agree that fixes should just be done
> as/when needed.  That is why I say "not judging, just noting" - I
> generally don't have the time to figure out if each and every unseen
> commit is a fix or new feature and/or if it has some possibility of
> interacting with some other tree in a way that a few days in linux-next
> may have flushed out.
>
> So, if you are happy with what you are doing (and you don't irritate
> Linus), then I am happy (as long as you don't cause unnecessary extra
> conflicts in linux-next :-)).
>

Maybe you could heuristic it by ratio new commits or new lines vs the
total size of the -next tree.

i.e. 59 commits in a 5000 commit tree is likely not that bad, 59
commits in a 20 commit tree would be bad.

Though not sure how you'd tune it!

Dave.
--
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/