develooper Front page | perl.perl4lib | Postings from March 2010

Re: Moving to Google Code/svn (was Re: [Patch] Escape marc tag/code/indicators in Marc::File::XML)

Thread Previous | Thread Next
From:
Galen Charlton
Date:
March 16, 2010 20:13
Subject:
Re: Moving to Google Code/svn (was Re: [Patch] Escape marc tag/code/indicators in Marc::File::XML)
Message ID:
66bd34b51003162013j376a4f3cl9c005d65f5d433fb@mail.gmail.com
Hi,

On Tue, Jan 26, 2010 at 11:57 AM, Ed Summers <ehs@pobox.com> wrote:
> I would argue for keeping stuff on sf.net ... and leapfrogging svn for
> git if we can.

To that end, I've enabled Git in the marcpm SourceForge project and
established a new repository which contains the history from the five
CVS modules (marc-charset, marc-lint, marc-marcmaker, marc-record,
marc-www, and marc-xml) merged into one Git repo.  Please note that I
chose to lump them together since the MARC/Perl modules are fairly
interdependent on one another, but if there's a general desire to have
a separate Git repo for each of the legacy CVS modules, I can set it
up that way instead.

The read-only git URL is

 git://marcpm.git.sourceforge.net/gitroot/marcpm/marcpm

The git URL for developers to push to is

ssh://YOURUSERNAME@marcpm.git.sourceforge.net/gitroot/marcpm/marcpm

Everybody who has commit access to the old CVS repositories should
have access to push to the Git repository.

The Git browse URL is

http://marcpm.git.sourceforge.net/git/gitweb.cgi?p=marcpm/marcpm;a=summary

For those who need it, numerous Git tutorials are just a web search
away, and I'm happy to help anybody who needs a hand getting started
with Git - drop me a line or ping me on #code4lib.

If there are no major objections, in a week's time I plan to make the
CVS repo read-only and we'll move forward with Git.

Regards,

Galen
-- 
Galen Charlton
gmcharlt@gmail.com

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About