Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: forrest-dev@xml.apache.org
From: Dave Brondsema <dave@brondsema.net>
Subject: [headsup] RE: forrest cvs->svn
Date: Tue, 2 Mar 2004 22:03:51 -0500
User-Agent: KMail/1.6
To: forrest-dev@xml.apache.org
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <200403022203.54287.dave@brondsema.net>

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

=2D ----------  Forwarded Message  ----------

Subject: RE: forrest cvs->svn
Date: Tuesday 02 March 2004 06:14 pm
=46rom: "Noel J. Bergman" <noel@devtech.com>
To: <pmc@xml.apache.org>
Cc: "Dave Brondsema" <dave@brondsema.net>, <infrastructure@apache.org>,=20
<fitz@apache.org>, "Sander Striker" <striker@apache.org>

I leave it to Sander or Fitz to do the cvs2svn work, but I setup
authorization based upon the avail file.  Each of the committers should run
svnpasswd to establish their SVN password.

There should not be any trouble importing the CVS module, so please wait for
that to happen.

	--- Noel

=2D -------------------------------------------------------


I didn't get a response to this infrastructure request a week ago, so I res=
ent=20
it.  In the process forrest-dev got off the cc:

So all committers need to set their SVN password and I will pass on the wor=
d=20
once the repository is created.  They'll probably remove write access to CV=
S=20
once that's done.


=2D --=20
Dave Brondsema
dave@brondsema.net
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFARUsZVvBSb5uzznARAmrZAKCK4cEVNZhzNlKDvMty5w2rHLO3pQCfebV5
LSBqeABmTCVpNx2fY6f8ECE=3D
=3DOdXG
=2D----END PGP SIGNATURE-----