linux-kernel - Re: [GIT]: Networking

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:	Wed, 20 Aug 2008 17:40:13 +0200
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	"John W. Linville" <linville@...driver.com>,
	David Miller <davem@...emloft.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	netdev@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT]: Networking

Hi Linus,

> > > again, my current understanding was that updates to the documentation
> > > that would help people to navigate and understand the kernel better and
> > > make it easier for them to do bug reports etc. are always welcome and
> > > should be pushed immediately. Same goes for new drivers that would
> > > enable people to use their hardware.
> > 
> > This is my (current) understanding as well.  If that is not the case,
> > then someone should clarify.
> 
> Guys, which part of "it wasn't any individual commit" didn' you 
> understand?
> 
> Why are you concentrating on one documentation commit that I didn't even 
> point to?
> 
> But that said - no, I don't think there is any reason to even push 
> documentation commits, unless there is a real and pressing reason (ie the 
> documentation is really important or will really matter from a future 
> merge standpoint). I generally won't complain about them, but I also don't 
> see the point.
> 
> I'd _much_ rather see you guys queue it up for future merges. 

John was just pointing out (like myself before) that a lot of people are
under the impression that documentation updates and new drivers should
not be queued up and merged as soon as possible.

I am really fine either way. Queuing them up is not a problem and you
made your point that you don't wanna see them after -rc1. That is fair
enough, but it really needs to be spelled our here since the overall
consensus is different. I will not send any of these do Dave anymore
after the merge window.

Regards

Marcel


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