From: Bernd Eckenfels <ecki-news2002-02@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18 - Full tarball is OK
Date: Tue, 26 Feb 2002 00:02:15 +0100 [thread overview]
Message-ID: <E16fU8N-0002FD-00@sites.inka.de> (raw)
In-Reply-To: <200202252149.g1PLnwe13182@directcommunications.net>
In article <200202252149.g1PLnwe13182@directcommunications.net> you wrote:
> So, I think, it's only patch-2.4.18 that has the problem...
Which is a pretty serious problem. Because ppl using patches hav different
source from ppl using tarball. This will get a lot of confusion for the 2.4.19
patch. I suggest to fix the 2.4.18 patch, even it this is not the best method
to keep unique version numbers.
Greetings
Bernd
next prev parent reply other threads:[~2002-02-25 23:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 21:49 Linux 2.4.18 - Full tarball is OK Chris Funderburg
2002-02-25 22:37 ` Alan Cox
2002-02-25 22:32 ` Rik van Riel
2002-02-25 22:40 ` H. Peter Anvin
2002-02-25 22:49 ` Alan Cox
2002-02-25 22:34 ` Beezly
2002-02-25 22:38 ` Dan Chen
2002-02-25 23:09 ` Alan Cox
2002-02-25 22:40 ` David Rees
2002-02-25 23:02 ` Bernd Eckenfels [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-25 21:49 Chris Funderburg
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=E16fU8N-0002FD-00@sites.inka.de \
--to=ecki-news2002-02@lina.inka.de \
--cc=linux-kernel@vger.kernel.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