Re: [Git migration] Old git repositories

2018-05-22 Thread Coty Sutherland
On Mon, May 21, 2018 at 3:57 PM, Mark Thomas wrote: > On 04/05/18 10:22, Konstantin Kolinko wrote: > > 2018-04-30 23:48 GMT+03:00 Mark Thomas : > >> The current plan is to merge all of the existing branches into a single > >> Git repo. This will be mirrored at GitHub under apache/tomcat. This is

Re: [Git migration] Old git repositories

2018-05-21 Thread Mark Thomas
On 04/05/18 10:22, Konstantin Kolinko wrote: > 2018-04-30 23:48 GMT+03:00 Mark Thomas : >> The current plan is to merge all of the existing branches into a single >> Git repo. This will be mirrored at GitHub under apache/tomcat. This is >> currently used for the svn mirror for trunk only. >> >> Thi

Re: [Git migration] Old git repositories

2018-05-04 Thread Konstantin Kolinko
2018-04-30 23:48 GMT+03:00 Mark Thomas : > The current plan is to merge all of the existing branches into a single > Git repo. This will be mirrored at GitHub under apache/tomcat. This is > currently used for the svn mirror for trunk only. > > This raises the question what to do with: > apache/tomc

Re: [Git migration] Old git repositories

2018-05-02 Thread Violeta Georgieva
2018-04-30 16:48 GMT-04:00 Mark Thomas : > > The current plan is to merge all of the existing branches into a single > Git repo. This will be mirrored at GitHub under apache/tomcat. This is > currently used for the svn mirror for trunk only. > > This raises the question what to do with: > apache/to

Re: [Git migration] Old git repositories

2018-05-02 Thread Huxing Zhang
+1 for deleting them. On Tue, May 1, 2018 at 5:36 AM, Coty Sutherland wrote: > On Mon, Apr 30, 2018, 16:48 Mark Thomas wrote: > >> The current plan is to merge all of the existing branches into a single >> Git repo. This will be mirrored at GitHub under apache/tomcat. This is >> currently used f

Re: [Git migration] Old git repositories

2018-04-30 Thread Coty Sutherland
On Mon, Apr 30, 2018, 16:48 Mark Thomas wrote: > The current plan is to merge all of the existing branches into a single > Git repo. This will be mirrored at GitHub under apache/tomcat. This is > currently used for the svn mirror for trunk only. > > This raises the question what to do with: > apa

[Git migration] Old git repositories

2018-04-30 Thread Mark Thomas
The current plan is to merge all of the existing branches into a single Git repo. This will be mirrored at GitHub under apache/tomcat. This is currently used for the svn mirror for trunk only. This raises the question what to do with: apache/tomcat7 apache/tomcat8 apache/tomcat85 I think there ar