Fwd: Welcome to gcc.gnu.org

Fwd: Welcome to gcc.gnu.org

[Diego Novillo]

Not sure who is in charge of the account assignment.  But the confirmation 
message sent out should be updated to mention SVN instead.


--------------------------------------------------------------------------
[ ... ]
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.

[ ... more CVS references here ... ]
--------------------------------------------------------------------------

Re: Fwd: Welcome to gcc.gnu.org

[Christopher Faylor]

On Wed, Nov 30, 2005 at 10:48:51AM -0500, Diego Novillo wrote:
>Not sure who is in charge of the account assignment.  But the confirmation 
>message sent out should be updated to mention SVN instead.
>
>
>--------------------------------------------------------------------------
>[ ... ]
>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@BLAH.  In special cases,
>we can be flexible on this requirement.
>
>[ ... more CVS references here ... ]
>--------------------------------------------------------------------------

The full text of a welcome message is below.

I'm not volunteering to change this for SVN.  It will be a headache having to
deal with both SVN and CVS.  Maybe the text should be modified to just point
to the gcc wiki.

If someone wants to make the appropriate modifications, the file to modify
in CVS is:

:ext:sourceware.org:/cvs/sourceware/infra/bin

This is a shell script.

cgf

Your account is now active, the login name is rkidd@BLAH.  Mail
sent to that address is forwarded to rkidd@BLAH.  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 have been assigned edit rights to the gcc Bugzilla bug reporting
database.  Your password is BLAH.

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@BLAH.  In special cases,
we can be flexible on this requirement.

Regarding SSH: If you have provided a Protocol 1 ssh key, you will need
to add the following lines to your a .ssh/config directory:

    Host gcc.gnu.org
	Protocol 1

This will cause your ssh connections to properly default to protocol 1
when connecting to gcc.gnu.org.  If you have provided "Protocol 2"
rsa/dsa keys, then no special action is required.


CVS  CVS is used for revision control.  If you are not familiar with CVS,
     you have some reading to do.  http://cvshome.org/ is the central
     source for all things CVS.  http://cvshome.org/docs/ has some
     useful information.

     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:rkidd@BLAH:/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@BLAH

     To get on a digest of the above list (get one note a day), send a 
     note to 

         gcc-cvs-digest-subscribe@BLAH

     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@BLAH

     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-cvs-wwwdocs-subscribe@BLAH


     If this is all a little confusing, just use the all-doing 
     auto-subscriber at <http://gcc.gnu.org/ml/>.

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 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
     the wwwdocs CVS module.  They will appear instantly (within three
     or four seconds, anyway) at http://gcc.gnu.org

If anything is unanswered, please ask your project mailing list.

Fwd: Welcome to gcc.gnu.org

[Mohan Embar]

Hi People,

I believe I erroneously applied for access to the "java"
repository instead of the "gcc" one. Could you please add
me to the "gcc" repository and send me confirmation of this?

-- Mohan

------- Start of forwarded message -------
From: root@sources.redhat.com
To: membar@sources.redhat.com
Cc: aph@redhat.com
Subject: Fwd: Welcome to gcc.gnu.org
Date: 7/21/2003 8:51:30 PM

Your account is now active, the login name is membar@gcc.gnu.org.
Mail sent to that address is forwarded to gnustuff@thisiscool.com.
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 have been assigned edit rights to the java Bugzilla bug reporting
database.  Your password is membarpass.

You should now have write access to the java 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.

Regarding SSH: If you have provided a Protocol 1 ssh key, you will need
to add the following lines to your a .ssh/config directory:

    Host gcc.gnu.org
	Protocol 1

This will cause your ssh connections to properly default to protocol 1
when connecting to gcc.gnu.org.  If you have provided "Protocol 2"
rsa/dsa keys, then no special action is required.


CVS  CVS is used for revision control.  If you are not familiar with CVS,
     you have some reading to do.  http://cvshome.org/ is the central
     source for all things CVS.  http://cvshome.org/docs/ has some
     useful information.

     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:membar@gcc.gnu.org:/cvs/java 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

         java-cvs-subscribe@gcc.gnu.org

     To get on a digest of the above list (get one note a day), send a 
     note to 

         java-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:

         java-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,

         java-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=java

HTTP All of the web pages on http://gcc.gnu.org/java/ are
     also under CVS.  You can create a home page (if one doesn't already
     exist) for java 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/java/

If anything is unanswered, please ask your project mailing list.

-------- End of forwarded message --------