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]

Message-ID: <20130716021349.GA26761@windriver.com>
Date:	Mon, 15 Jul 2013 22:13:50 -0400
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
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>
Subject: Re: [PATCH] Documentation: update references to v2.6.x in
 development-process

[Re: [PATCH] Documentation: update references to v2.6.x in development-process] On 16/07/2013 (Tue 10:15) Stephen Rothwell wrote:

> Hi Paul,
> 
> Good work!
> 
> On Mon, 15 Jul 2013 19:34:44 -0400 Paul Gortmaker <paul.gortmaker@...driver.com> wrote:
> >
> >  Linux-next trees are announced on the linux-kernel and linux-next mailing
> >  lists when they are assembled; they can be downloaded from:
> >  
> > -	http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/
> > +	https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/
> 
> Maybe:
> 
> "	git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> 
> Or as patches relative to Linus' latest -rc or releases from:
> 
> 	https://www.kernel.org/pub/linux/kernel/next/
> 
> Or viewed online at:
> 
> 	https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/
> "
> 
> Or maybe that is a bit verbose.

Probably no harm in it.  I'd cc'd you and akpm for exactly that reason;
I wasn't sure I'd updated to the authoratative source.  I'll fold that
into a v2 once there has been a chance for other feedback to come in.

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?

Thanks,
Paul.
--

> -- 
> Cheers,
> Stephen Rothwell                    sfr@...b.auug.org.au

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