[M3devel] "fork"

[Dragiša Durić]

Absolutely preserved. That's a reason why our choices are svn and git - there are great migration tools.

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



On Apr 22, 2013, at 5:20 AM, Tony Hosking wrote:

> What happens to all the commit logs? I'd hate to lose those. They carry useful information. 
> 
> Sent from my iPhone
> 
> On 21/04/2013, at 5:54 PM, Peter McKinna <peter.mckinna at gmail.com> wrote:
> 
>> Hi,
>> 
>>   I too support a clean move to git  Great tool-set, very fast. 
>> 
>> The swig guys recently did a similar move to git,  hosting it on github and all went very smoothly.
>> 
>> Regards 
>> 
>> Peter
>> 
>> 
>> On Sun, Apr 21, 2013 at 3:33 PM, Dragiša Durić <dragisha at m3w.org> wrote:
>> Well, this changes situation :). If nobody insists on CVS, then single jump from CVS to GIT is all we need. 
>> 
>> --
>> Dragiša Durić
>> dragisha at m3w.org
>> 
>> 
>> 
>> On Apr 20, 2013, at 9:11 PM, Olaf Wagner wrote:
>> 
>>> In contrast to what I said two or three years ago, I now think that
>>> a migration away from CVS is overdue, but I haven't had the time to do it
>>> right and probably won't have that time in the near future. We _do_ have
>>> several svn and git experts in our company, but I haven't been able
>>> to inspire them to do the migration yet.
>>> 
>>> Actually I think that the migration itself will be not very difficult; it is
>>> the Hudson/Jenkins/Apache/scripts support that will mostly need to be
>>> rewritten wrt. version control. I doubt that anybody outside of Elego has
>>> done much work on that.
>>> 
>>> I'd like to try to acquire some internal ressources again; so I'd ask
>>> you to wait for some weeks. If I haven't been able to organize something
>>> until June, I'd think it will be best if someone else takes over completely.
>> 
>> 

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