linux-kernel - Re: [PATCH] Documentation: update references to v2.6.x in development-process

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, 17 Jul 2013 09:34:08 -0400
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	Jonathan Corbet <corbet@....net>
CC:	Rob Landley <rob@...dley.net>, <linux-doc@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, Willy Tarreau <w@....eu>,
	Ben Hutchings <ben@...adent.org.uk>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH] Documentation: update references to v2.6.x in development-process

On 13-07-16 01:33 PM, Jonathan Corbet wrote:
> On Mon, 15 Jul 2013 19:34:44 -0400
> Paul Gortmaker <paul.gortmaker@...driver.com> wrote:
> 
>> The last mainline release of a v2.6.x kernel was back in May 2011.
>> Here we update references to be 3.x based, which also means updating
>> some dates and statistics.
> 
> Ccing the author of the document never hurts :)

It might be worth sticking an entry in MAINTAINERS for that dir.
If one had asked me who wrote it, I probably would have recalled that
info, but instead I just out of habit ran get_maintainers...

> 
> I actually went through this exercise a while back, but somehow never got
> around to sending the changes out into the world.  Easily distracted, I
> guess.  Anyway, you can put my Acked-by on your changes if you like.

Thanks.

> 
>> On a similar note, I was thinking about the recent thread on linux-next
>> where we were indicating that people shouldn't rebase linux-next content
>> on a whim, and that new devel (vs. bugfix) content shouldn't appear in
>> the linux-next content during the merge window.  There is no question
>> that the linux-next process is integral to the main flow of patches to
>> mainline, so I think Documentation/development-process/2.Process (the
>> same file) should also capture those points in the linux-next section.
>> Do you have some pre-canned text we can insert there, or should I draft
>> something up for you to review?
> 
> Seems useful, I could also try to help with this if you run out of steam.
> I'd be more inclined to put it into section 7, though, since it's the sort
> of thing early-stage developers don't normally need to worry about.

I'd agree with that; a pointer in section two where linux-next is 1st
mentioned can point to section7 where the advanced info is given.  

Paul.
--

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