From: bame@riverrock.org
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] 2.4.0 Source Import
Date: Tue, 09 Jan 2001 11:33:45 -0700 [thread overview]
Message-ID: <m14G3ac-001Vp3C@chalet> (raw)
I've imported 2.4.0 sources into our CVS tree, safely isolated on the
vendor branch so theoretically nobody should see any changes until they
ask for them. WE ARE NOT FOR MERGING AT THIS TIME -- it's to allow people
to use CVS (esp. cvs diff and tkdiff) to examine and prepare for what's
changed. We are planning to merge with whatever is reasonable, which may
not be 2.4.0, around Jan 23, so consider this import only a courtesy.
If you want to see what's changed between 2.4.0test10 and 2.4.0, use
tkdiff -rLINUS_240_TEST10 -rLINUS_240 <filename>
(or use cvs diff if you prefer). If you want to see what a CVS
automatic merge would do, use:
cvs update -jLINUS_240_TEST10 -jLINUS_240
on your top-of-branch tree. PLEASE DON'T COMMIT MERGED BITS unless
you build a consensus it won't interfere with ongoing development or the
upcoming merge.
NOTE: CVS documentation suggests using a command something like
cvs update -jlinus:yesterday -jlinus
to merge a recent import. That WON'T WORK in our tree.
-Paul Bame
reply other threads:[~2001-01-09 18:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m14G3ac-001Vp3C@chalet \
--to=bame@riverrock.org \
--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 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.