public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Coywolf Qi Hunt <coywolf@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Matthias Urlichs <smurf@smurf.noris.de>
Subject: Re: 2.6.16-rc2-mm1
Date: Sat, 11 Feb 2006 04:05:58 +0800	[thread overview]
Message-ID: <2cd57c900602101205s7a884ce2w@mail.gmail.com> (raw)
In-Reply-To: <20060210112530.540fec62.akpm@osdl.org>

2006/2/11, Andrew Morton <akpm@osdl.org>:
> Coywolf Qi Hunt <coywolf@gmail.com> wrote:
> >
> > 2006/2/8, Andrew Morton <akpm@osdl.org>:
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc2/2.6.16-rc2-mm1/
> > >
> > >
> > > - Should also be available at:
> > >
> > >         git://git.kernel.org/pub/scm/linux/kernel/git/smurf/linux-trees.git
> > >
> > >   browseable at:
> > >
> > >         ftp://ftp.kernel.org/pub/scm/linux/kernel/git/smurf/linux-trees.git
> > >
> > >   thanks to a script which Matthias Urlichs <smurf@smurf.noris.de> has
> > >   prepared.  I haven't tried this, so please let us know how it goes.
> >
> > The master branch seems not correct. It should be v2.6.16-rc2-mm1, but
> > it is v2.6.13-rc4-mm1 or something.

"v2.6.15-mm3" actually.

> >
>
> There is a 2.6.16-rc2-mm1 tag in there.  Perhaps Matthias could describe
> how things are organised, recommendations for how people should use that
> tree?
>

We should use "tags" for particular releases, and just one "master" branch.
--
Coywolf Qi Hunt

  reply	other threads:[~2006-02-10 20:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08  6:06 2.6.16-rc2-mm1 Andrew Morton
2006-02-08 21:17 ` 2.6.16-rc2-mm1 Paul Jackson
2006-02-10 10:34   ` 2.6.16-rc2-mm1 Sachin Sant
2006-02-10  0:37 ` [-mm patch] drivers/scsi/gdth.c: make __gdth_execute() static Adrian Bunk
2006-02-10 13:11   ` Christoph Hellwig
2006-02-10  0:41 ` [-mm patch] drivers/message/fusion/mptctl.c: make struct async_queue static Adrian Bunk
2006-02-10  0:43 ` [-mm patch] drivers/video/geode/video_gx.c: make struct gx_pll_table_48MHz static Adrian Bunk
2006-02-10 12:31 ` [-mm patch] fs/xfs/linux-2.6/xfs_linux.h: #if CONFIG_SMP -> #ifdef CONFIG_SMP Adrian Bunk
2006-02-10 14:52 ` Radeonfb ignores video= parameter [was: Re: 2.6.16-rc2-mm1] Mattia Dongili
2006-02-10 15:14   ` [PATCH] fbdev: Fix typo in fbmem.c Antonino A. Daplas
2006-02-10 16:34     ` Mattia Dongili
2006-02-10 18:17 ` 2.6.16-rc2-mm1 Coywolf Qi Hunt
2006-02-10 19:25   ` 2.6.16-rc2-mm1 Andrew Morton
2006-02-10 20:05     ` Coywolf Qi Hunt [this message]
2006-02-10 20:22     ` 2.6.16-rc2-mm1 Matthias Urlichs
2006-02-10 21:30 ` 2.6.16-rc2-mm1 Jim Crilly
2006-02-10 22:25   ` 2.6.16-rc2-mm1 Andrew Morton
2006-02-10 22:34     ` 2.6.16-rc2-mm1 Dave Jones
2006-02-10 22:28   ` 2.6.16-rc2-mm1 Jeff Garzik
2006-02-10 22:30     ` 2.6.16-rc2-mm1 Jim Crilly
2006-02-10 21:55 ` 2.6.16-rc2-mm1 Pavel Machek
2006-02-11 20:31 ` 2.6.16-rc2-mm1 Martin Hermanowski
2006-02-11 21:41   ` 2.6.16-rc2-mm1 Andrew Morton
2006-02-11 22:27     ` 2.6.16-rc2-mm1 Martin Hermanowski
2006-02-11 23:34       ` 2.6.16-rc2-mm1 Andrew Morton
2006-02-12 12:10         ` 2.6.16-rc2-mm1 Martin Hermanowski
2006-02-13 23:30 ` 2.6.16-rc2-mm1: crash on suspend Laurent Riffard
2006-02-14  0:57 ` 2.6.16-rc2-mm1 Alexandre Buisse
2006-02-14  0:51   ` 2.6.16-rc2-mm1 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=2cd57c900602101205s7a884ce2w@mail.gmail.com \
    --to=coywolf@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smurf@smurf.noris.de \
    /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