From: Andrew Morton <akpm@osdl.org>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: wli@holomorphy.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc4-mm1
Date: Sun, 15 May 2005 02:54:29 -0700 [thread overview]
Message-ID: <20050515025429.11cda9a2.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0505151142520.2387@dragon.hyggekrogen.localhost>
Jesper Juhl <juhl-lkml@dif.dk> wrote:
>
> On Sat, 14 May 2005, Andrew Morton wrote:
>
> > William Lee Irwin III <wli@holomorphy.com> wrote:
> > >
> > > On Thu, May 12, 2005 at 03:31:00AM -0700, Andrew Morton wrote:
> > > > +uml-remove-elfh.patch
> > > > +uml-critical-change-memcpy-to-memmove.patch
> > > > UML important updates
> > >
> > > uml-remove-elfh looks empty.
> >
> > Yeah, I couldn't work out a way of generating a patch which removes a
> > zero-length file, so that's there as a reminder to ask Linus to remove the
> > thing by hand.
> >
> This works :
>
> --- linux-2.6.12-rc4-mm1-orig/include/asm-um/elf.h 2005-05-14 12:54:27.000000000 +0200
> +++ linux-2.6.12-rc4-mm1/include/asm-um/elf.h 2005-05-15 11:39:28.000000000 +0200
> @@ -0,0 +1 @@
> +
> --- linux-2.6.12-rc4-mm1/include/asm-um/elf.h 2005-05-15 11:39:28.000000000 +0200
> +++ /dev/null 2005-05-15 11:17:24.000000000 +0200
> @@ -1 +0,0 @@
> -
That's cheating, too. Plus rediffing this patch will make it disappear.
next prev parent reply other threads:[~2005-05-15 9:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 10:31 2.6.12-rc4-mm1 Andrew Morton
2005-05-12 12:21 ` 2.6.12-rc4-mm1, build results compared to 2.6.12-rc3-mm3 Jan Dittmer
2005-05-13 6:19 ` Maneesh Soni
2005-05-12 12:39 ` 2.6.12-rc4-mm1 Reuben Farrelly
2005-05-12 15:09 ` 2.6.12-rc4-mm1 Andrew Morton
2005-05-14 21:19 ` 2.6.12-rc4-mm1 Andrew James Wade
2005-05-12 12:58 ` kobject_register failed for intelfb (-EACCES) (Re: 2.6.12-rc4-mm1) Alexey Dobriyan
2005-05-12 15:43 ` Greg KH
2005-05-12 15:59 ` Andrew Morton
2005-05-12 16:04 ` Greg KH
2005-05-12 16:20 ` Alexey Dobriyan
2005-05-12 18:14 ` [PATCH -mm] Print KBD and AUX irqs correctly Alexey Dobriyan
2005-05-12 21:42 ` [-mm patch] mm.h: fix page_zone compile error Adrian Bunk
2005-05-12 22:09 ` Dave Hansen
2005-05-12 22:26 ` Adrian Bunk
2005-05-13 13:26 ` Andy Whitcroft
2005-05-12 21:54 ` 2.6.12-rc4-mm1 Greg KH
2005-05-13 0:47 ` [-mm patch] drivers/cpufreq/cpufreq_conservative.c: make cpufreq_gov_dbs static Adrian Bunk
2005-05-13 7:24 ` 2.6.12-rc4-mm1 Dave Airlie
2005-05-13 7:25 ` 2.6.12-rc4-mm1 Dave Airlie
2005-05-13 14:53 ` 2.6.12-rc4-mm1 steve
2005-05-13 18:12 ` [-mm patch] kprobes: arch_supports_kretprobes cleanup Frederik Deweerdt
2005-05-13 19:40 ` 2.6.12-rc4-mm1 Johannes Stezenbach
2005-05-14 11:27 ` 2.6.12-rc4-mm1 Richard Purdie
2005-05-16 11:27 ` 2.6.12-rc4-mm2 Richard Purdie
2005-05-15 1:20 ` 2.6.12-rc4-mm1 William Lee Irwin III
2005-05-15 1:30 ` 2.6.12-rc4-mm1 Andrew Morton
2005-05-15 9:44 ` 2.6.12-rc4-mm1 Jesper Juhl
2005-05-15 9:54 ` Andrew Morton [this message]
2005-05-15 9:43 ` 2.6.12-rc4-mm1: drivers/usb/gadget/ether.c compile error Adrian Bunk
2005-05-16 15:26 ` David Brownell
2005-05-15 11:32 ` [-mm patch] arch/i386/Kconfig: SELECT_MEMORY_MODEL -> ARCH_SELECT_MEMORY_MODEL Adrian Bunk
2005-05-15 18:24 ` Dave Hansen
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=20050515025429.11cda9a2.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
/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;
as well as URLs for NNTP newsgroup(s).