From: Mark Mitchell <mark@codesourcery.com>
To: gcc-announce@gcc.gnu.org
Subject: GCC now uses Subversion, instead of CVS
Date: Sun, 30 Oct 2005 19:34:00 -0000 [thread overview]
Message-ID: <4365201A.9020405@codesourcery.com> (raw)
If you build snapshots directly from the FSF source repositories, you
should be aware that GCC is now using the Subversion source control
system, instead of CVS.
We made this change because we believe Subversion will make it easier
for us to continue to improve GCC.
For information about using Subversion to access the GCC source code
repository, please see:
http://gcc.gnu.org/svn.html
Tthis change does not affect the format for source releases and
snapshots; they will still be provided as compressed TAR files in the
usual way, and will be, for the most part, indistinguishable from the
versions generated from CVS.
Daniel Berlin deserves the credit for leading this conversion, with
assistance from a large team of volunteers.
We'd also like to thank the developers of Subversion with providing us
with such a powerful tool, and the developers of CVS for providing us
with a tool that served us so well for such a long time.
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
reply other threads:[~2005-10-30 19:34 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=4365201A.9020405@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc-announce@gcc.gnu.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).