From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18 - Full tarball is OK
Date: 25 Feb 2002 14:40:31 -0800 [thread overview]
Message-ID: <a5eegv$10o$1@cesium.transmeta.com> (raw)
In-Reply-To: <E16fTkG-0006VG-00@the-village.bc.nu> <Pine.LNX.4.33L.0202251931360.7820-100000@imladris.surriel.com>
Followup to: <Pine.LNX.4.33L.0202251931360.7820-100000@imladris.surriel.com>
By author: Rik van Riel <riel@conectiva.com.br>
In newsgroup: linux.dev.kernel
>
> On Mon, 25 Feb 2002, Alan Cox wrote:
>
> > If so Marcelo can you put up 2.4.18-fixed patch and a borked-fixed diff ?
> That would break hpa's incremental diff patches.
> If somebody needs 2.4.18 + fix, they can just run 2.4.18-rc4.
>
Since the tarball apparently is OK and it's only the patch that's
different, just re-create the patch, put it in the proper place, and
make sure the file date on the patch is different; the incremental
diff will be regenerated to match.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-02-25 22:41 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 [this message]
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
-- 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='a5eegv$10o$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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 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.