From: willy@thepuffingroup.com
To: Paul Bame <bame@endor.fc.hp.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] 2.3.99pre1 merge CANCELLED
Date: Fri, 17 Mar 2000 13:17:59 -0500 [thread overview]
Message-ID: <20000317131759.G27942@thepuffingroup.com> (raw)
In-Reply-To: <E12W0Op-0002kk-00@endor.fc.hp.com>; from Paul Bame on Fri, Mar 17, 2000 at 10:18:59AM -0700
On Fri, Mar 17, 2000 at 10:18:59AM -0700, Paul Bame wrote:
> = There have now been reported several problems with the 2.3.99pre1
> = release, so prumpf is right that we should hold off merging for now.
> = Once there is a stable 2.3.99preX release, we should merge to that
> = kernel since it has been some time since our last merge.
>
> We could use this opportunity to start removing our SOM __setup
> hacks since we're now based on ELF?
Certainly.
next prev parent reply other threads:[~2000-03-17 19:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-15 19:03 [parisc-linux] Merge with Linus 2.3.99pre1 willy
2000-03-15 19:28 ` Michael Ang
2000-03-16 11:15 ` Philipp Rumpf
2000-03-16 15:27 ` willy
2000-03-17 1:12 ` [parisc-linux] 2.3.99pre1 merge CANCELLED Michael Ang
2000-03-17 17:18 ` Paul Bame
2000-03-17 18:17 ` willy [this message]
2000-03-17 18:19 ` Bryan W. Headley
2000-03-17 19:28 ` Jason Eckhardt
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=20000317131759.G27942@thepuffingroup.com \
--to=willy@thepuffingroup.com \
--cc=bame@endor.fc.hp.com \
--cc=parisc-linux@thepuffingroup.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