> On Jan 20, 2019, at 8:57 AM, sebb wrote:
>
> On Sun, 20 Jan 2019 at 13:44, Gary Gregory wrote:
>>
>> I think the simplest would be to migrate them all. Then we can forget all
>> of that svn tree and mark it as read-only.
>
> +1
>
> It will make it easier to find things if they are all in
On Sun, 20 Jan 2019 at 13:44, Gary Gregory wrote:
>
> I think the simplest would be to migrate them all. Then we can forget all
> of that svn tree and mark it as read-only.
+1
It will make it easier to find things if they are all in one place.
> Gary
>
> On Sun, Jan 20, 2019 at 6:48 AM Rob Tomp
I think the simplest would be to migrate them all. Then we can forget all
of that svn tree and mark it as read-only.
Gary
On Sun, Jan 20, 2019 at 6:48 AM Rob Tompkins wrote:
>
>
> > On Jan 20, 2019, at 4:08 AM, sebb wrote:
> >
> >> On Sun, 20 Jan 2019 at 03:53, Rob Tompkins wrote:
> >>
> >> H
> On Jan 20, 2019, at 4:08 AM, sebb wrote:
>
>> On Sun, 20 Jan 2019 at 03:53, Rob Tompkins wrote:
>>
>> Hey guys,
>>
>> I’m curious if you saw my conversation with Chris Lambertus over in INFRA
>> about what to do with our SVN repos [1]? I’m not quite sure what to do now
>> that we have t
On Sun, 20 Jan 2019 at 03:53, Rob Tompkins wrote:
>
> Hey guys,
>
> I’m curious if you saw my conversation with Chris Lambertus over in INFRA
> about what to do with our SVN repos [1]? I’m not quite sure what to do now
> that we have the vote [2], to move the repos over. It seems that they want
Hey guys,
I’m curious if you saw my conversation with Chris Lambertus over in INFRA about
what to do with our SVN repos [1]? I’m not quite sure what to do now that we
have the vote [2], to move the repos over. It seems that they want to “freeze”
svn and make it read only in the migration. Do we
