mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: unlisted-recipients:; (no To-header on input)@pop.zip.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.18 almost...
Date: Sun, 10 Dec 2000 10:36:37 +1100	[thread overview]
Message-ID: <3A32C205.E773B900@eyal.emu.id.au> (raw)
In-Reply-To: <E144syy-0005sE-00@the-village.bc.nu> <20001209161254.H954@opus.bloom.county>

On Sat, Dec 09, 2000 at 11:00:41PM +0000, Alan Cox wrote:

> The patch I intend to be 2.2.18 is out as 2.2.18pre26 in the usual place.
> I'll move it over tomorrow if nobody reports any horrors, missing files etc

The text leading up to this was:
--------------------------
|diff -u --new-file --recursive --exclude-from /usr/src/exclude
v2.2.17/arch/i386/vmlinux.lds linux/arch/i386/vmlinux.lds
|--- v2.2.17/arch/i386/vmlinux.lds      Wed May  3 21:22:13 2000
|+++ linux/arch/i386/vmlinux.lds        Sat Dec  9 21:23:21 2000
--------------------------
File to patch: 
Skip this patch? [y] y
1 out of 1 hunk ignored

--
Eyal Lebedinsky		(eyal@eyal.emu.id.au)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-10  0:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-09 23:00 Alan Cox
2000-12-09 23:12 ` Tom Rini
2000-12-09 23:36   ` Eyal Lebedinsky [this message]
2000-12-09 23:32 ` Michael Rothwell
2000-12-10  0:17   ` Keith Owens
2000-12-10  0:23   ` Andre Hedrick
2000-12-10  1:11   ` Alan Cox
2000-12-10  8:29   ` Tigran Aivazian
2000-12-10  8:34     ` Tigran Aivazian
2000-12-10 18:20     ` Alan Cox
2000-12-10 16:34 ` Vasil Kolev
2000-12-11  9:26 ` Eddy
2000-12-11 13:03   ` Alan Cox
2000-12-11 10:44 Luca Montecchiani

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=3A32C205.E773B900@eyal.emu.id.au \
    --to=eyal@eyal.emu.id.au \
    --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

all inboxes | Powered by JetHome®