Re: Summary: Migration from svn to git

2014-10-16 Thread Martin Grigorov
Hi, On Thu, Oct 16, 2014 at 9:38 PM, Konstantin Kolinko wrote: > Just several technical notes, > > > If anyone wants to comment on Github, I think that it is already > possible. I think that it works and the messages are forwarded to the > dev list. > > Unfortunately this is not true. At the mo

Re: Summary: Migration from svn to git

2014-10-16 Thread Mark Thomas
On 16/10/2014 18:46, Konstantin Kolinko wrote: > 2014-10-16 21:23 GMT+04:00 Mark Thomas : >> On 07/10/2014 15:14, Mark Thomas wrote: >>> The following is a summary of the previous discussions and the concerns >>> raised. It is an attempt to get all the information in one place so we >>> can agree o

Re: Summary: Migration from svn to git

2014-10-16 Thread Konstantin Kolinko
Just several technical notes, 2014-10-07 18:14 GMT+04:00 Mark Thomas : > 2. We would migrate to a two git repo that - initially would have the > following mapping to the current svn repo: >tomcat git repo > trunk -> master > tc7.0.x/trunk -> 7.0.x > tc6.0.x/trunk -> 6.0

Re: Summary: Migration from svn to git

2014-10-16 Thread Konstantin Kolinko
2014-10-16 21:23 GMT+04:00 Mark Thomas : > On 07/10/2014 15:14, Mark Thomas wrote: >> The following is a summary of the previous discussions and the concerns >> raised. It is an attempt to get all the information in one place so we >> can agree on whether or not we want to migrate to git. > > Given

Re: Summary: Migration from svn to git

2014-10-16 Thread Mark Thomas
On 07/10/2014 15:14, Mark Thomas wrote: > The following is a summary of the previous discussions and the concerns > raised. It is an attempt to get all the information in one place so we > can agree on whether or not we want to migrate to git. Given the lack of feedback on this thread, my working

Re: Summary: Migration from svn to git

2014-10-07 Thread Mark Thomas
On 07/10/2014 15:14, Mark Thomas wrote: > The following is a summary of the previous discussions and the concerns > raised. It is an attempt to get all the information in one place so we > can agree on whether or not we want to migrate to git. Comments in-line. > 1. ... No specific issues with a