From: Sam Ravnborg <sam@ravnborg.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Greg Ungerer <gerg@snapgear.com>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Steven King <sfking00@yahoo.com>,
uClinux development list <uclinux-dev@uclinux.org>,
Greg Ungerer <gerg@uclinux.org>,
Greg Ungerer <gregungerer@westnet.com.au>
Subject: Re: merge of m68knommu and m68k arch branches?
Date: Mon, 21 Feb 2011 22:57:19 +0100 [thread overview]
Message-ID: <20110221215719.GA24535@merkur.ravnborg.org> (raw)
In-Reply-To: <201102212243.15867.arnd@arndb.de>
On Mon, Feb 21, 2011 at 10:43:15PM +0100, Arnd Bergmann wrote:
> On Friday 18 February 2011 13:01:53 Greg Ungerer wrote:
> > >> Attached is a script and patch that does a kind of brute force
> > >> simplistic merge of the directories and files. (Thanks to Stephen King
> > >> <sfking@fdwdc.com> for the initial version of this script, and to
> > >> Sam Ravnborg for the m68k includes merge script this was based on).
> > >> Nothing outside of the arch/m68k and arch/m68knommu directories is
> > >> touched, and in the end there is no more arch/m68knommu. To apply you
> > >> simply run the script from the top of a current kernel git tree (I used
> > >> 2.6.38-rc5 for testing) and then apply the patch.
> > >
> > > The initial version of said script was created by Arnd IIRC.
> >
> > Apologies to Arnd then :-)
>
> I had absolutely no memory of having done said script, but if Sam
> says wrote it did, that's probably true.
>
> I was just about to say how much I like your script when I read
> that it was my idea...
See semi original version in: 49148020bcb6910ce71417bd990a5ce7017f9bd3
Sam
next prev parent reply other threads:[~2011-02-21 21:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 0:07 merge of m68knommu and m68k arch branches? Greg Ungerer
2011-02-18 7:44 ` Sam Ravnborg
2011-02-18 12:01 ` Greg Ungerer
2011-02-21 21:43 ` Arnd Bergmann
2011-02-21 21:57 ` Sam Ravnborg [this message]
2011-02-18 11:27 ` Geert Uytterhoeven
2011-02-18 15:24 ` Geert Uytterhoeven
2011-02-18 22:12 ` Greg Ungerer
2011-02-19 8:39 ` Geert Uytterhoeven
2011-02-20 23:53 ` Greg Ungerer
2011-02-21 7:41 ` Geert Uytterhoeven
2011-03-17 23:59 ` Greg Ungerer
2011-03-18 7:24 ` Geert Uytterhoeven
2011-02-21 21:18 ` Thomas Gleixner
2011-02-22 2:05 ` Greg Ungerer
2011-02-22 7:14 ` Geert Uytterhoeven
2011-02-22 7:29 ` Sam Ravnborg
2011-02-22 7:40 ` Geert Uytterhoeven
2011-02-22 8:04 ` Sam Ravnborg
2011-02-22 9:16 ` Thomas Gleixner
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=20110221215719.GA24535@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=arnd@arndb.de \
--cc=gerg@snapgear.com \
--cc=gerg@uclinux.org \
--cc=gregungerer@westnet.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sfking00@yahoo.com \
--cc=uclinux-dev@uclinux.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