http://markmail.org/search/?q=list%3Aorg.codehaus.mojo.dev%20git#

On the first page you'll already see a couple of threads about this.
IMHO we should have only one type of repository, not one half through GIT and the rest through SVN. Since this would mean a huge migration this should be done scripted/automated.

For GIT users there are several ways to work with SVN, so that's probably why this isn't that urgent.

Robert

On Thu, 27 Jun 2013 21:44:33 +0200, Lennart Jörelid <[email protected]> wrote:

Folks... if anyone has an answer to this question, I would be all ears.
Can I work with GIT or Mercurial here? Onto some mirror?
If not - is there a process to distribute projects/plugins to GitHub?


2013/6/25 Lennart Jörelid <[email protected]>

Hello all,

I wonder if the Mojo project has a structured way of migrating to a
distributed VCS (GIT, presumably, or Mercurial) for various currently
SVN-based projects - or any policy on a 2-way mirroring between the two
VCS'es.

I believe distributed VCSs increase visibility and reduce complexity for
donning a patch compared to the standard subversion way, particularly with
the help of processes and services such as GitHub or BitBucket. Anything
that can increase visibility and reduce hinders in contributing patches to
projects is in itself a Good Thing.

So ... is there a Git/Mercurial mirror or migration process for SVN
projects at Codehaus?
If so - where can I find access details?
If not - why?

--

+==============================+
| Bästa hälsningar,
| [sw. "Best regards"]
|
| Lennart Jörelid
| EAI Architect & Integrator
|
| jGuru Europe AB
| Mölnlycke - Kista
|
| Email: [email protected]
| URL:   www.jguru.se
| Phone
| (skype):    jgurueurope
| (intl):     +46 708 507 603
| (domestic): 0708 - 507 603
+==============================+






--
Using Opera's revolutionary email client: http://www.opera.com/mail/

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email


Reply via email to