From: Philipp Rumpf <prumpf@inwestnet.de>
To: willy@thepuffingroup.com
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Merge with Linus 2.3.99pre1
Date: Thu, 16 Mar 2000 12:15:25 +0100 [thread overview]
Message-ID: <20000316121525.H673@abacus.local> (raw)
In-Reply-To: <20000315140309.U27942@thepuffingroup.com>; from willy@thepuffingroup.com on Wed, Mar 15, 2000 at 02:03:09PM -0500
On Wed, Mar 15, 2000 at 02:03:09PM -0500, willy@thepuffingroup.com wrote:
> Linus released 2.3.99pre1 today which marks the start of the 2.4
> release effort. We'd like to merge Linus' changes into our tree on
> Friday, starting around 11am EST (8am PST, 4pm UTC, 5pm CET).
I don't think merging with 2.3.99pre1 before verifying it works on at least
one other non-x86 architecture is a good idea. I'd also prefer it if someone
tried nfsroot aso with it before.
Wouldn't it be a good idea to choose a kernel that has been released for more
than 2 days for merging ?
> If you have any local changes which can go back into our tree, now would be a
> good time to commit them.
I do, but am still waiting for reactions to the Assembly Language Changes
thread.
> If you're in the middle of something which
> will be disrupted by this, now would also be a good time to shout `STOP'.
My changes can as easily be merged after we moved to 2.3.99pre1 as they can
now.
Philipp
next prev parent reply other threads:[~2000-03-16 12:14 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 [this message]
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
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=20000316121525.H673@abacus.local \
--to=prumpf@inwestnet.de \
--cc=parisc-linux@thepuffingroup.com \
--cc=willy@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 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.