Changes to Git repository - Multiple Repositories now supported

CSL Development
1

Ah, this is actually really useful (since distributed SCMs don’t have
the subproject support of CVS and SVN). Guess it doesn’t matter now
though …---------- Forwarded message ----------
From: SourceForge.net Team noreply@sourceforge.net
Date: Tue, Aug 25, 2009 at 3:35 PM
Subject: Changes to Git repository - Multiple Repositories now supported

Hello! You’re receiving this message because your SourceForge project uses
Git.

We have some good news and some bad news. First, the good news: As of
2009-08-20, each project can now have multiple Git source repositories.
The bad news? We’ve moved some stuff around, and it will probably mean a
bit of reconfiguration for you.

Since each project can have multiple Git repositories, we’ve updated the
URLs for accessing your gitweb interface so that you can specify the
repository name. For example:

http://projectname.git.sf.net/git/gitweb.cgi?p=projectname/reponame

The repository you were using before we made this change has been given a
repository name that’s the same as your project name, so it can be found
here:

http://projectname.git.sf.net/git/gitweb.cgi?p=projectname/projectname.

If you visit http://yourproject.git.sf.net/, you will now be given a list
of your project’s repositories.

A similar adjustment is also necessary for the URLs you use to access your
Git repository. For example, a “git clone” command should now look
something like this:

git clone
ssh://username@projectname.git.sourceforge.net/gitroot/projectname/reponame

Unfortunately, this breaks any links you may have made to the gitweb
interface, so you’ll need to change them. You also may want to notify your
community about the changed location of your Git repository. We apologize
for the extra work, but we couldn’t keep the same naming structure for all
SCMs without some breakage.

You may have noticed that your project’s feed data is in the process of
being regenerated, and some of your Git events may be missing. We hope to
empty and regenerate the Project Feed data relating to Git for all projects
by the end of this week.

If you’ve got any questions regarding these URL changes, please don’t
hesitate to contact us: http://sourceforge.net/support

Thanks for reading,
The SourceForge.net Crew

SourceForge.net has made this mailing to you as a registered user of
the SourceForge.net site to convey important information regarding
your SourceForge.net account or your use of SourceForge.net services.

We make a small number of directed mailings to registered users each
year regarding their account or data, to help preserve the security of
their account or prevent loss of data or service access.

If you have concerns about this mailing please contact our Support
team per: http://sourceforge.net/support

2

since distributed SCMs don’t have
the subproject support of CVS and SVN

By ‘subproject’ are you referring to svn:externals? Git has support
for ‘submodules’ which apparently serve roughly the same purpose.

Regards,
Robert.2009/8/25 Bruce D’Arcus <@Bruce_D_Arcus1>:

3

No. I mean that with xbib svn, it’s easy to just checkout, say, the
csl directory, which looks like its own repository, with its own tags
and branches.

You can’t do that with git/darcs/hg; it’s all or nothing.

Bruce