public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Marcos D. Marado Torres" <marado@student.dei.uc.pt>
Cc: Dominik Karall <dominik.karall@gmx.net>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	chrisw@osdl.org, Linus Torvalds <torvalds@osdl.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: Linux 2.6.11.2
Date: Wed, 9 Mar 2005 07:35:48 -0800	[thread overview]
Message-ID: <20050309153548.GA23096@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0503091023410.7496@student.dei.uc.pt>

On Wed, Mar 09, 2005 at 10:28:32AM +0000, Marcos D. Marado Torres wrote:
> On Wed, 9 Mar 2005, Dominik Karall wrote:
> 
> >>>> which is a patch against the 2.6.11.1 release.  If consensus arrives
> >>>> that this patch should be against the 2.6.11 tree, it will be done that
> >>>> way in the future.
> >>>
> >>> IMHO it sould be against 2.6.11 and not 2.6.11.1, like -rc's that are'nt
> >>> againt
> >>> the last -rc but against 2.6.x.
> >>
> >> It's a stable release, not a pre/rc, so against 2.6.11.1 sounds most
> >> logical to me.
> >
> > I don't think so. The latest patch (2.6.11.2 now) is on the frontpage of
> > kernel.org, so IMHO the user should not need to search the kernel.org/pub
> > archives to get 2.6.11.1 patch before he can start working with 2.6.11.2.
> >
> > I think it's a small problem too, that 2.6.11 source isn't directly accessable
> > through the kernel.org frontpage while there is no "full tarball" of 2.6.11.X
> > trees.
> 
> With that "full tarball" for 2.6.11.X the issues would be over.
> I think there should be one.

There is one, did you not look?

	kernel.org/pub/linux/kernel/v2.6/linux-2.6.11.2.tar.gz

thanks,

greg k-h

  parent reply	other threads:[~2005-03-09 15:36 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  8:39 Linux 2.6.11.2 Greg KH
2005-03-09  8:39 ` Greg KH
2005-03-17 15:18   ` Gene Heskett
2005-03-09  9:52 ` Marcos D. Marado Torres
2005-03-09 10:04   ` Geert Uytterhoeven
2005-03-09 10:17     ` Marcos D. Marado Torres
2005-03-09 10:41       ` Geert Uytterhoeven
2005-03-09 11:23         ` Jesper Juhl
2005-03-09 21:26       ` Wakko Warner
2005-03-09 10:21     ` Dominik Karall
2005-03-09 10:28       ` Marcos D. Marado Torres
2005-03-09 10:51         ` Adrian Bunk
2005-03-09 15:35         ` Greg KH [this message]
2005-03-09 11:11   ` Pavel Machek
2005-03-09 23:57     ` Matt Mackall
2005-03-10  5:16       ` Willy Tarreau
2005-03-11 18:45       ` Bill Davidsen
2005-03-11 19:08         ` Matt Mackall
2005-03-11 19:19           ` Chris Wright
2005-03-11 22:01             ` Greg KH
2005-03-14 17:10               ` Bill Davidsen
2005-03-14 17:32                 ` Greg KH
2005-03-15 20:38           ` Bill Davidsen
2005-03-16  8:56             ` David Greaves
2005-03-09 12:38 ` Andy Whitcroft
2005-03-09 14:03 ` Marcelo Tosatti
2005-03-09 18:38   ` Greg KH
2005-03-09 20:32 ` Bill Davidsen
2005-03-09 21:06 ` Matt Mackall
2005-03-09 21:21   ` Randy.Dunlap
2005-03-09 23:11   ` Greg KH
2005-03-09 23:38     ` Matt Mackall
2005-03-10 12:54     ` Gene Heskett
2005-03-11 19:23       ` Bill Davidsen
2005-03-11 23:33         ` Gene Heskett
2005-03-11 14:53 ` Krzysztof Halasa
2005-03-11 17:38   ` Chris Wright
2005-03-11 19:28     ` Bill Davidsen
2005-03-11 21:07     ` Krzysztof Halasa
2005-03-11 21:11       ` Chris Wright
     [not found] <fa.dan38um.1m4gojq@ifi.uio.no>
     [not found] ` <fa.animhpl.r201hh@ifi.uio.no>
2005-03-10  1:46   ` Bodo Eggert
2005-03-10  3:08     ` Matt Mackall

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=20050309153548.GA23096@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=dominik.karall@gmx.net \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marado@student.dei.uc.pt \
    --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