public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Randy Dunlap" <rdunlap@xenotime.net>
To: Jesper Juhl <jesper.juhl@gmail.com>,
	Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.13-rc4
Date: Fri, 29 Jul 2005 09:55:38 -0700	[thread overview]
Message-ID: <1122656138.19704@shark.he.net> (raw)



> On 7/29/05, Linus Torvalds <torvalds@osdl.org> wrote:
> > 
> > Hey everybody,
> > 
> >  as many of you are aware, we were talking (not enough) about the
release
> > process at LKS this year.
> > 
> > This ain't it.
> > 
> > This is just the regular old release "process", with some LKS
backlog put
> > in for good measure.
> > 
> > But the good news is, that I'll try the new release process after 2.6.13
> > is out, which is hopefully not too far away. Which means that we should
> > try to let people know about the fact that if they want to merge stuff,
> > they should do so in the first two weeks after the 2.6.13 release,
and no
> > later (also, no earlier either, by now).
> > 
> 
> For the bennefit of those of us who were not at LKS, could someone
> elaborate a bit on "the new release process" ?


It's summarized here:
http://lwn.net/Articles/144281/

---
~Randy

             reply	other threads:[~2005-07-29 16:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29 16:55 Randy Dunlap [this message]
2005-07-29 17:00 ` Linux 2.6.13-rc4 Jesper Juhl
  -- strict thread matches above, loose matches on Subject: below --
2005-07-29 12:09 Mickey Stein
2005-07-29 19:01 ` Cal Peake
2005-07-30  1:32   ` Mickey Stein
2005-07-30  1:53   ` Mickey Stein
2005-07-28 23:34 Linus Torvalds
2005-07-29 16:48 ` Jesper Juhl
2005-07-29 23:41   ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1122656138.19704@shark.he.net \
    --to=rdunlap@xenotime.net \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox