From: Craig Rodrigues <rodrigc@mediaone.net>
To: overseers@gcc.gnu.org
Cc: rodrigc@sourceware.cygnus.com, law@redhat.com
Subject: Re: Welcome to gcc.gnu.org
Date: Sat, 10 Mar 2001 22:22:00 -0000 [thread overview]
Message-ID: <20010311012139.A16564@mediaone.net> (raw)
In-Reply-To: <20010228034610.11379.qmail@sourceware.cygnus.com>
Hi,
This gives me access to GCC CVS, but how do I get access to GNATS?
Thanks.
--
Craig Rodrigues
http://www.gis.net/~craigr
rodrigc@mediaone.net
On Wed, Feb 28, 2001 at 03:46:10AM -0000, root@sourceware.cygnus.com wrote:
> Your account is now active, the login name is rodrigc@gcc.gnu.org.
> Mail sent to that address is forwarded to rodrigc@mediaone.net. This
> forwarding is a convenience so that people who reply directly to CVS
> commit mail notes will not get a bounce--publicize it at your own risk.
> If your involvement with the project ends at some point, the mail address
> will become invalid and I will laugh evilly as people try in vain to
> reach you.
>
> You should now have write access to the gcc repository with
> SSH+cvs. Here are lots of details about how to do things.
>
> You don't have general shell access, just CVS remote access. Just about
> everything can be done via CVS. If there is some special requirement
> that you have where you need shell access, talk to your project's lead
> and have them talk to overseers@gcc.gnu.org. In special cases,
> we can be flexible on this requirement.
>
>
>
> CVS CVS is used for revision control. If you are not familiar with CVS,
> you have some reading to do. http://www.cyclic.com/ is the central
> source for all things CVS. http://www.cyclic.com/cvs/info.html has
> various information. I don't see any simple introductions on using
> CVS, so ask if you have questions. The most important thing is this:
> When you want to do a check-in of some change, do it like this:
>
> % cvs update
> % cvs diff # carefully verify what you're about to check in!
> % cvs commit
>
> All of the sources are under CVS. You have write access to the
> files in your repository. Check them out like this:
>
> export CVS_RSH=ssh
> cvs -z9 -d :ext:rodrigc@gcc.gnu.org:/cvs/gcc co gcc
>
> After you've checked out some files, you won't need to specify the
> CVSROOT (-d) again, it will be picked out of the CVS control files
> (the CVS/Root file). You will need to include the -z9; you can put
> it in your $HOME/.cvsrc file ("cvs -z9") or add it to your command
> line whenever you're doing CVS operations.
>
> If you're going over a modem, you'll definitely want to get this
> as compressed as possible.
>
> To avoid the nuisance of having to supply your passphrase for each
> operation, you may want to use ssh-agent(1) followed by ssh-add(1)
> and entering your passphrase once for all. Either start your
> session as a child of ssh-agent or run it as a demon and set the
> values of the environment variables SSH_AUTHENTICATION_SOCKET and
> SSH_AGENT_PID in each relevant process to what ssh-agent prints
> when it starts. To avoid messages about (lack of) X11 forwarding,
> put in your $HOME/.ssh/config and entry like:
>
> Host gcc.gnu.org
> ForwardX11 no
>
> CVS COMMIT MESSAGES
> You can get e-mail notifications for when things are checked in to
> your group's repository. There are two notification mailing lists,
> one for the web pages for your project and one for the project
> source files. To subscribe to your source-file-notification list,
> send a message to
>
> gcc-cvs-subscribe@gcc.gnu.org
>
> To get on a digest of the above list (get one note a day), send a
> note to
>
> gcc-cvs-digest-subscribe@gcc.gnu.org
>
> The body/Subject are ignored in these messages. The From: address
> is the one you a requesting to subscribe. To request an arbitrary
> address be subscribed, say foo@bar.com, send a note like this:
>
> gcc-cvs-subscribe-foo=bar.com@gcc.gnu.org
>
> If your project has a web page, then there is a second mailing
> list for notifications about changes to them. The addresses are
> just like the above ones except they include "-webpages" after the
> project name. For instance,
>
> gcc-webpages-cvs-digest-subscribe@gcc.gnu.org
>
>
> If this is all a little confusing, just use the all-doing
> auto-subscriber at
> http://gcc.gnu.org/ml/lists.html#faqs
>
> CVSWEB You can browse changes that are being made to the CVS repository by
> going to
>
> http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc?cvsroot=gcc
>
> HTTP All of the web pages on http://gcc.gnu.org/gcc/ are
> also under CVS. You can create a home page (if one doesn\'t already
> exist) for gcc by putting files in the htdocs/ directory of
> your CVS repository. They will appear instantly (within three or
> four seconds, anyway) at http://gcc.gnu.org/gcc/
>
> If anything is unanswered, please ask.
next parent reply other threads:[~2001-03-10 22:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010228034610.11379.qmail@sourceware.cygnus.com>
2001-03-10 22:22 ` Craig Rodrigues [this message]
2001-03-10 23:43 ` Gerald Pfeifer
[not found] <20030122174634.21612.qmail@sources.redhat.com>
2003-01-22 20:53 ` Gerald Pfeifer
2003-01-22 23:28 ` Jason Molenda
2003-01-22 23:40 ` Christopher Faylor
2003-01-23 0:09 ` Benjamin Kosnik
[not found] <20030222192240.25884.qmail@sources.redhat.com>
2003-02-22 19:42 ` Steven Bosscher
[not found] <20030915134556.13277.qmail@sources.redhat.com>
2003-10-01 9:43 ` Dorit Naishlos
2003-10-01 9:54 ` Gerald Pfeifer
2003-10-01 11:38 ` Dorit Naishlos
2003-10-01 11:22 ` Joseph S. Myers
2003-10-01 12:02 ` Christopher Faylor
2003-10-02 21:43 ` Gerald Pfeifer
2003-10-03 4:01 ` Christopher Faylor
[not found] <20030605212847.10833.qmail@sources.redhat.com>
2005-09-08 8:59 ` Daniel Towner
2005-09-08 19:53 ` Ian Lance Taylor
[not found] <20130924144729.26557.qmail@sourceware.org>
2013-11-22 12:04 ` Paulo Matos
[not found] <20141217152934.16213.qmail@sourceware.org>
2014-12-18 22:21 ` Sebastian Huber
2014-12-19 16:14 ` Joel Sherrill
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=20010311012139.A16564@mediaone.net \
--to=rodrigc@mediaone.net \
--cc=law@redhat.com \
--cc=overseers@gcc.gnu.org \
--cc=rodrigc@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).