[M3devel] "fork"

[Dragiša Durić]

Also monotone, Bazaar, mercurial… :)

From fossil-users mailing list:
> > Please guide me how do I convert CVS repository to fossil,  
> > preserving history and branches / tags.
> 
> There is no generalized procedure for doing this.  To convert SQLite  
> from CVS to fossil, I wrote a TCL script that checked out each  
> historical version of of SQL from CVS then checked it back into  
> fossil.  It took several hours to run.

I don't know where you got this information on "Linux only"? See http://git-scm.com/downloads

If someone has better proposal, then please respond. 

--
Dragiša Durić
dragisha at m3w.org



On Apr 20, 2013, at 8:53 PM, microcode at zoho.com wrote:

> Hi, what about fossi? (fossil-scm.org). It has a lot of nice features,
> builds anywhere (unlike GIT which is hell to build anywhere but Linux) and
> is from the author of SQLite- code is small and dead simple.
> 
> 
> On Sat, Apr 20, 2013 at 12:52:58PM +0200, Dragi??a Duri?? wrote:
>> We have this situation where Elego does not have neither interest nor resources to spare to do version control system migration. Projects like GCC and GNOME have abandoned CVS for good, and they are only  two on a very long list.
>> 
>> My idea is basically to do this migration/fork without actually doing one.  In short:
>>  * We convert existing CVS to SVN, make CVS repository "read-only" i.e. single writer.
>>  * Do all our work on SVN,
>>  * Use svn2cvs  to save SVN commits back to our "read-only" CVS repo.
>> 
>> This way we get the best of both worlds. We have up-to-date CVS so all of our current infrastructure simply works. Process outlined  is based on well-tested tools so we have little to no worries there. And we have as modern version control system as we can have without a distributed one.
>> 
>> My first choice is  SVN as a target because of easy way to maintain  mirrored CVS repo, and thus reuse existing infrastructure. 
>> 
>> We can also use GIT in one of two scenarios:
>> * Go straight from CVS to GIT, never look back;
>> * add svn2git step to first "recipe" and use  git2svn to sync back to svn repository from first step. 
>> 
>> This second variant looks like an overkill, but there are tools to maintain bidirectional mirroring of single git branch to a svn repo (esp. if this mirroring tools is only writer to svn repo). And all this is needed only in case we need (and I suppose we do) to maintain live CVS.
>> 
>> I believe Elego will have no problems to extend their already great contribution to Modula-3 with few gigabytes of disk space and few configured processes. I would happily contribute my time and expertise to help with additional workload, and I am sure I am not only one willing to help. 
>> 
>> Thanks for reading this! :)
>> dd
>> 
>> --
>> Dragi??a Duri??
>> dragisha at m3w.org
>> 
>> 
>> 
> 
> 
> 
> -- 
>        _                             _      
> ._ _ _ <_> ___  _ _  ___  ___  ___  _| | ___ 
> | ' ' || |/ | '| '_>/ . \/ | '/ . \/ . |/ ._>
> |_|_|_||_|\_|_.|_|  \___/\_|_.\___/\___|\___.
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20130420/a790221a/attachment-0002.html>