From: Dan Malek <dan@embeddededge.com>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: Beginning Merger Patch
Date: Tue, 2 Aug 2005 19:12:05 -0400 [thread overview]
Message-ID: <f316a2ceff0d79bb6cf9d8530555496b@embeddededge.com> (raw)
In-Reply-To: <20050802230537.GA9125@gate.ebshome.net>
On Aug 2, 2005, at 7:05 PM, Eugene Surovegin wrote:
> Hmm, I got an impression that we wouldn't touch ppc and ppc64 for
> now and just _copy_ or create clean stuff into powerpc. I think this
> will be much safer, at least at the beginning.
Shouldn't this be a 2.7 project?
-- Dan
next prev parent reply other threads:[~2005-08-02 23:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 22:59 Beginning Merger Patch Jon Loeliger
2005-08-02 23:05 ` Eugene Surovegin
2005-08-02 23:12 ` Dan Malek [this message]
2005-08-02 23:17 ` Eugene Surovegin
2005-08-03 3:08 ` Paul Mackerras
2005-08-03 2:38 ` Josh Boyer
2005-08-02 23:10 ` Dan Malek
2005-08-05 7:47 ` [PATCH] 1/2 Start header file merger (Was: Re: Beginning Merger Patch) Stephen Rothwell
2005-08-05 7:50 ` [PATCH] 2/2 merge the easy ones Stephen Rothwell
2005-08-05 8:37 ` [PATCH] 1/2 Start header file merger (Was: Re: Beginning Merger Patch) Stephen Rothwell
2005-08-05 9:08 ` Michael Ellerman
2005-08-05 11:53 ` Arnd Bergmann
2005-08-05 14:59 ` Stephen Rothwell
2005-08-05 16:24 ` Arnd Bergmann
2005-08-26 20:55 ` Jon Loeliger
2005-08-29 15:44 ` Segher Boessenkool
2005-08-29 18:41 ` Christopher Friesen
2005-08-17 5:39 ` Kumar Gala
2005-08-17 11:05 ` Arnd Bergmann
2005-08-03 2:17 ` Beginning Merger Patch Nathan Lynch
2005-08-03 2:58 ` Eugene Surovegin
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=f316a2ceff0d79bb6cf9d8530555496b@embeddededge.com \
--to=dan@embeddededge.com \
--cc=ebs@ebshome.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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.