From: Russ Cox <rsc@swtch.com>
To: 9fans <9fans@9fans.net>
Subject: plan9port, drawterm cvs deprecated - use mercurial
Date: Tue, 8 Dec 2009 12:10:27 -0800 [thread overview]
Message-ID: <dd6fe68a0912081210k2cb1f3b4mb2b2d4812afa29d5@mail.gmail.com> (raw)
If you're using CVS to get plan9port or drawterm,
it's time to switch to Mercurial.
http://swtch.com/plan9port/man/man1/hg.html
More detail follows, for those who care.
In November 2007 I added support for fetching
Plan 9 from User Space via Mercurial instead
of CVS. For the past two years I've been keeping
both repositories in sync, but I am no longer able
to do so--the chewing gum and duct tape holding
them together has broken yet again and I am not
going to bother trying to fix it. I have changed the
copy of INSTALL in the CVS repository to point
at the Mercurial instructions, and I will leave the
CVS repository alone for at least a few months before
deleting it. The drawterm situation is the same,
although there the Mercurial repository is a more
recent arrival.
If you need to install Mercurial, I've found that
"sudo easy_install mercurial" works on both
Linux and OS X and installs a newer version
than apt-get does on Ubuntu.
Sorry for the inconvenience.
Russ
P.S. If you are already using Mercurial for plan9port,
please check your $PLAN9/.hg/hgrc file and
make sure the "default =" line reads
default = http://code.swtch.com/plan9port/
If you were an early Mercurial adopter, you might
instead have a line like
default = http://hg.pdos.csail.mit.edu/hg/plan9/ # NOT THIS
If so, edit the file to make it use the first URL.
next reply other threads:[~2009-12-08 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 20:10 Russ Cox [this message]
2009-12-09 13:12 ` [9fans] " kokamoto
2009-12-09 14:56 ` Anthony Sorace
2009-12-10 10:51 ` kokamoto
2009-12-11 4:27 ` Russ Cox
2009-12-11 12:50 ` kokamoto
2009-12-11 12:36 ` kokamoto
2009-12-21 11:56 ` kokamoto
2009-12-09 19:14 ` Tim Newsham
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=dd6fe68a0912081210k2cb1f3b4mb2b2d4812afa29d5@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).