mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH 0/6] kill i386 and x86_64 directories
Date: Fri, 26 Oct 2007 07:39:26 -0700	[thread overview]
Message-ID: <20071026073926.25dc56dc@laptopd505.fenrus.org> (raw)
In-Reply-To: <20071026062336.GA19253@uranus.ravnborg.org>

On Fri, 26 Oct 2007 08:23:36 +0200
Sam Ravnborg <sam@ravnborg.org> wrote:

> On Thu, Oct 25, 2007 at 10:17:53PM +0200, Thomas Gleixner wrote:
> > 
> > I think the last remaining bit to cleanup is the symlink from
> > arch/x86/boot/bzImage. Now that the old directories are gone it does
> > not make much sense to keep them alive. Andrew will survive it :)
> 
> It is not just Andrew I'm afraid.
> We got a Debian bug-report too when we did not have the symlink and I
> asume this is true for several others.
> We should let it stay in 2.6.24 and remove the symlink for 2.6.25 IMO.

that's the worst of all things to do... either make a change in ONE go,
when you do all the changes anyway (users will remmeber 2.6.24 was the
unification kernel, but 2.6.25 breaking stuff will be a total
surprise)... or keep them around forever. As long as it works, nobody
will change the scripts.

  parent reply	other threads:[~2007-10-26 14:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 19:56 Sam Ravnborg
2007-10-25 20:03 ` [PATCH 1/6] x86: move i386 and x86_64 Makefiles to arch/x86 Sam Ravnborg
2007-10-25 20:03 ` [PATCH 2/6] x86: move defconfig files for i386 and x86_64 to x86 Sam Ravnborg
2007-10-25 20:04 ` [PATCH 3/6] x86: unification of i386 and x86_64 Kconfig.debug Sam Ravnborg
2007-10-25 23:30   ` Yinghai Lu
2007-10-25 23:35     ` Randy Dunlap
2007-10-25 23:52       ` H. Peter Anvin
2007-10-26  1:55         ` Yinghai Lu
2007-10-26  4:29     ` Sam Ravnborg
2007-10-25 20:05 ` [PATCH 4/6] kconfig: small code refactoring in kconfig Makefile Sam Ravnborg
2007-10-25 20:05 ` [PATCH 5/6] x86: move i386 and x86_64 Kconfig files to x86 directory Sam Ravnborg
2007-10-26  1:53   ` Yinghai Lu
2007-10-26  2:46     ` Randy Dunlap
2007-10-26  5:51       ` Yinghai Lu
2007-10-26  6:02         ` Randy Dunlap
2007-10-26  6:14         ` Sam Ravnborg
2007-10-26  6:39           ` Yinghai Lu
2007-10-26  6:58             ` Sam Ravnborg
2007-10-25 20:06 ` [PATCH 6/6] x86: kill the old i386 and x86_64 directories Sam Ravnborg
2007-10-25 20:14 ` [PATCH 0/6] kill " Sam Ravnborg
2007-10-25 20:19   ` Kay Sievers
2007-10-25 20:36     ` Sam Ravnborg
2007-10-25 20:17 ` Thomas Gleixner
2007-10-25 21:12   ` [GIT PULL] " Sam Ravnborg
2007-10-26  6:23   ` [PATCH 0/6] " Sam Ravnborg
2007-10-26 12:01     ` Alan Cox
2007-10-26 14:39     ` Arjan van de Ven [this message]
     [not found] <9ih2i-qd-15@gated-at.bofh.it>
     [not found] ` <9ihlw-193-21@gated-at.bofh.it>
2007-10-26  3:30   ` Bodo Eggert

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=20071026073926.25dc56dc@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=sam@ravnborg.org \
    --cc=tglx@linutronix.de \
    /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®