All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Bowler <nbowler@elliptictech.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.37-rc1
Date: Mon, 1 Nov 2010 11:47:17 -0400	[thread overview]
Message-ID: <20101101154717.GA17893@elliptictech.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1011011634240.2566@localhost6.localdomain6>

On 2010-11-01 16:37 +0100, Thomas Gleixner wrote:
> On Mon, 1 Nov 2010, Linus Torvalds wrote:
> > The merge window for 2.6.37 is over, and -rc1 is out there (or will be
> > soon, as things are uploading from my laptop here in Boston and then
> > mirroring out)
> 
> Did you switch back to tarballs and patches only or is there going to
> be an update of your git tree in the foreseeable future ?

Seems that the v2.6.37-rc1 tag is in the git tree, but is not reachable
from the master branch.  See

  http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=shortlog;h=v2.6.37-rc1

-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

  reply	other threads:[~2010-11-01 15:47 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 12:07 Linux 2.6.37-rc1 Linus Torvalds
2010-11-01 15:37 ` Thomas Gleixner
2010-11-01 15:47   ` Nick Bowler [this message]
2010-11-01 15:52     ` Ryusuke Konishi
2010-11-01 16:07       ` Linus Torvalds
2010-11-02 18:51 ` Linux 2.6.37-rc1 (acpi_video) Randy Dunlap
2010-11-03 21:08 ` Linux 2.6.37-rc1 (cciss: remove_proc_entry warning) Randy Dunlap
2010-11-03 21:15 ` Linux 2.6.37-rc1 (pcrypt fault) Randy Dunlap
2010-11-03 21:15   ` Randy Dunlap
2010-11-10 11:21   ` Steffen Klassert
2010-11-10 18:11     ` Randy Dunlap
2010-11-03 21:21 ` Linux 2.6.37-rc1 (net/sched: cls_cgroup) Randy Dunlap
2010-11-03 21:21   ` Randy Dunlap
2010-11-03 22:01   ` Eric Dumazet
2010-11-03 22:01     ` Eric Dumazet
2010-11-03 22:19     ` Li Zefan
2010-11-03 22:19       ` Li Zefan
2010-11-03 22:31       ` Li Zefan
2010-11-03 22:31         ` Li Zefan
2010-11-03 23:31     ` Herbert Xu
2010-11-03 23:31       ` Herbert Xu
2010-11-04  1:46       ` Li Zefan
2010-11-04  1:46         ` Li Zefan
2010-11-04  1:56       ` David Miller
2010-11-04  1:56         ` David Miller
2010-11-04 15:56       ` Randy Dunlap
2010-11-03 23:16 ` Linux 2.6.37-rc1 (floppy module load: no device found) Randy Dunlap
2010-11-05 22:10   ` Linus Torvalds
2010-11-05 22:12     ` David Miller
2010-11-05 23:03     ` Randy Dunlap
2010-11-05 23:36       ` Linus Torvalds
2010-11-06  0:33         ` Randy Dunlap
2010-11-06 12:16         ` Vivek Goyal
2010-11-06 14:52           ` Linus Torvalds
2010-11-03 23:18 ` Linux 2.6.37-rc1 (libipw remove_proc_entry warning) Randy Dunlap
2010-11-05 22:24   ` Linus Torvalds
2010-11-05 23:06     ` Randy Dunlap
2010-11-05 23:38       ` Linus Torvalds
2010-11-08 21:33         ` John W. Linville
2010-11-03 23:20 ` Linux 2.6.37-rc1 (scsi_debug: list corruption) Randy Dunlap
2010-11-03 23:20   ` Randy Dunlap
2010-11-04  2:25   ` Xiaotian Feng
2010-11-04  2:25     ` Xiaotian Feng
2010-11-04 16:12     ` Randy Dunlap

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=20101101154717.GA17893@elliptictech.com \
    --to=nbowler@elliptictech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.