public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: first tree
Date: Thu, 14 Feb 2008 20:39:13 +0200	[thread overview]
Message-ID: <47B48AD1.9010105@panasas.com> (raw)
In-Reply-To: <86802c440802141029w5b409b9bl6a2dbc377ea913f2@mail.gmail.com>

On Feb. 14, 2008, 20:29 +0200, "Yinghai Lu" <yhlu.kernel@gmail.com> wrote:
> On Thu, Feb 14, 2008 at 5:35 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> Hi all,
>>
>>  I have created the first cut of the linux-next tree at
>>  git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
>>
>>  Things to know about this tree:
>>
>>  It has two branches - master and stable.  Stable is currently just Linus'
>>  tree and will never rebase.  Master will rebase on an almost daily basis
>>  (maybe slower at the start).
> 
> can you make stable rebase too?

The point is that if you rebase it it's no longer stable.

Benny

> 
> so we make git-bisect working by fold in some obvious bug fix.
> 
> or that is linux-stable tree?
> 
> YH
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2008-02-14 18:39 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14 13:35 linux-next: first tree Stephen Rothwell
2008-02-14 14:06 ` Jiri Kosina
2008-02-14 14:34   ` Stephen Rothwell
2008-02-14 14:45 ` Rafael J. Wysocki
2008-02-14 15:00   ` Stephen Rothwell
2008-02-14 15:25     ` Martin Schwidefsky
2008-02-14 21:48       ` Stephen Rothwell
2008-02-14 15:49     ` Paul Mundt
2008-02-14 21:58       ` Stephen Rothwell
2008-02-14 15:54     ` Dave Kleikamp
2008-02-14 22:01       ` Stephen Rothwell
2008-02-15  4:58     ` Len Brown
2008-02-15  6:19       ` Stephen Rothwell
2008-02-14 16:04 ` Andy Whitcroft
2008-02-20 14:23   ` Stephen Rothwell
2008-02-20 16:47     ` Randy Dunlap
2008-02-22  0:07       ` Frank Seidel
2008-02-22  0:12         ` Randy Dunlap
2008-02-22  0:22           ` Harvey Harrison
2008-02-22  5:31           ` Frank Seidel
2008-02-22  0:15         ` Greg KH
2008-02-22  5:33           ` Frank Seidel
2008-02-22  0:28         ` Stephen Rothwell
2008-02-22  5:41           ` Frank Seidel
2008-02-22  5:55             ` Stephen Rothwell
2008-02-14 17:38 ` Mauro Carvalho Chehab
2008-02-14 22:24   ` Stephen Rothwell
2008-02-18 16:07     ` Mauro Carvalho Chehab
2008-02-14 18:29 ` Yinghai Lu
2008-02-14 18:39   ` Benny Halevy [this message]
2008-02-14 20:20 ` Greg KH
2008-02-14 20:50   ` Sam Ravnborg
2008-02-14 23:52     ` Stephen Rothwell
2008-02-14 23:31   ` Stephen Rothwell
2008-02-14 20:23 ` Sam Ravnborg
2008-02-14 23:35   ` Stephen Rothwell
2008-02-14 21:03 ` Jeff Garzik
2008-02-14 21:05   ` Jeff Garzik
2008-02-14 21:26   ` James Bottomley
2008-02-14 21:45     ` Jeff Garzik
2008-02-14 23:58   ` Stephen Rothwell
2008-02-14 22:27 ` Trond Myklebust
2008-02-15  0:33   ` Stephen Rothwell
2008-02-15 21:00   ` J. Bruce Fields
2008-02-16 15:37     ` Stephen Rothwell
2008-02-14 23:17 ` David Chinner
2008-02-15  0:50   ` Stephen Rothwell
2008-02-15  1:10     ` David Chinner
2008-02-15  2:14       ` Stephen Rothwell
2008-02-15  8:33 ` Bryan Wu
2008-02-16 15:33   ` Stephen Rothwell
2008-02-17  2:23     ` Robin Getz
2008-02-17  5:33       ` Stephen Rothwell
2008-02-16 15:13 ` Stefan Richter
2008-02-16 15:40   ` Stephen Rothwell
2008-02-17 19:09 ` Mark M. Hoffman
2008-02-17 23:27   ` Stephen Rothwell
2008-02-18  8:04 ` Artem Bityutskiy
2008-02-18  8:29   ` Stephen Rothwell
2008-02-18 11:11 ` Paolo Ciarrocchi
2008-02-18 13:15   ` Stephen Rothwell

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=47B48AD1.9010105@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=yhlu.kernel@gmail.com \
    /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