public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Andersen <anddan@linux-user.net>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH] README (resend) - Explain new 2.6.xx.x version number
Date: Wed, 15 Sep 2004 04:25:36 +0200	[thread overview]
Message-ID: <4147A820.5090107@linux-user.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0409150255590.981@scrub.home>

Roman Zippel wrote:
> Hi,
> 
> On Tue, 14 Sep 2004, Daniel Andersen wrote:
> 
> 
>>This one ended up in the void last time without any comments.
> 
> 
> The funny thing is by the time people managed to apply the patch 
> correctly, they don't need to read the README anymore.
> Seriously, without knowing about the pre-patches, what would you expect 
> about the patch order if you found the patches 2.6.8, 2.6.8.1, 2.6.9?
> 
> bye, Roman

I'm not sure what you really mean to say. And I'm not expecting 
anything. I wrote the patch because I see people ask, even on this list, 
if 2.6.9 is to be applied against 2.6.8 or 2.6.8.1. Whats the trouble?

Daniel Andersen

--

  reply	other threads:[~2004-09-15  2:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-14 21:35 [PATCH] README (resend) - Explain new 2.6.xx.x version number Daniel Andersen
2004-09-14 21:43 ` Dave Jones
2004-09-14 22:23   ` Daniel Andersen
2004-09-15  1:02 ` Roman Zippel
2004-09-15  2:25   ` Daniel Andersen [this message]
2004-09-15  2:40   ` Randy.Dunlap
2004-09-15  8:01     ` Denis Vlasenko
2004-09-15 11:06     ` Roman Zippel
2004-09-15 15:25       ` Randy.Dunlap
2004-09-15 15:57         ` Roman Zippel

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=4147A820.5090107@linux-user.net \
    --to=anddan@linux-user.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=zippel@linux-m68k.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