Re: [Git migration] Existing PRs

2018-01-22 Thread Mark Thomas
On 19/01/18 10:38, Violeta Georgieva wrote: > 2018-01-18 22:40 GMT+02:00 Mark Thomas : >> >> Hi, >> >> This issue might have resolved itself. We currently only have open PRs >> on the apache/tomcat github repo. Assuming that repo would be made >> read/write (I'm checking with

Re: [Git migration] Existing PRs

2018-01-19 Thread Violeta Georgieva
2018-01-18 22:40 GMT+02:00 Mark Thomas : > > Hi, > > This issue might have resolved itself. We currently only have open PRs > on the apache/tomcat github repo. Assuming that repo would be made > read/write (I'm checking with infra) then there isn't a problem. > > If anyone opnes

Re: [Git migration] Existing PRs

2018-01-18 Thread Coty Sutherland
On Thu, Jan 18, 2018 at 3:40 PM, Mark Thomas wrote: > Hi, > > This issue might have resolved itself. We currently only have open PRs > on the apache/tomcat github repo. Assuming that repo would be made > read/write (I'm checking with infra) then there isn't a problem. > > If

[Git migration] Existing PRs

2018-01-18 Thread Mark Thomas
Hi, This issue might have resolved itself. We currently only have open PRs on the apache/tomcat github repo. Assuming that repo would be made read/write (I'm checking with infra) then there isn't a problem. If anyone opnes a PR on one of the other repos between now and migration we can simply