From: "Frank Ch. Eigler" <fche@redhat.com>
To: Adriaan van Os <adriaan@microbizz.nl>
Cc: overseers@gcc.gnu.org
Subject: Re: ping
Date: Wed, 29 Mar 2006 12:12:00 -0000 [thread overview]
Message-ID: <20060329121213.GI599@redhat.com> (raw)
In-Reply-To: <98e82889384a9395dbb131a664089966@microbizz.nl>
Hi -
On Wed, Mar 29, 2006 at 08:42:11AM +0200, Adriaan van Os wrote:
> [...]
> Now that gcc moved from cvs to svn, I would like to create a GNU Pascal
> branch for the gcc repository. [...]
> I read at <http://gcc.gnu.org/svnwrite.html#branches> how to create a
> branch, but my understanding is that svn write access is needed [...]
Once your copyright assignment is complete, and if you can get a gcc
maintainer to sponsor a CVS/SVN account for you, you can follow the
usual GCC procedure to get it created. <http://gcc.gnu.org/svnwrite.html>
- FChE
next prev parent reply other threads:[~2006-03-29 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 6:42 ping Adriaan van Os
2006-03-29 12:12 ` Frank Ch. Eigler [this message]
2006-03-29 14:20 ` ping Adriaan van Os
2006-03-29 14:26 ` ping Frank Ch. Eigler
-- strict thread matches above, loose matches on Subject: below --
2000-12-30 6:08 Ping Mikael Djurfeldt
2000-08-25 11:55 ` Ping Mikael Djurfeldt
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=20060329121213.GI599@redhat.com \
--to=fche@redhat.com \
--cc=adriaan@microbizz.nl \
--cc=overseers@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).