Hi Massimo

Thanks for the migration. On setting all the SVN repos to r/o: I remember when 
we had to do a security fix long after mod_tcl was abandoned and I was recently 
asked to do patch for Websh (which I didn't so far, but it's still kind of on 
the bucket list :-)...)

On one hand putting everything to r/o clearly indicates: not supported anymore, 
on the other hand it's preventing any future action on the other projects. 
Would it be possible to only close the rivet repo on SVN?

Gruess
Ronnie
--
Ronnie Brunner | 
ronnie.brun...@netcetera.com<mailto:ronnie.brun...@netcetera.com> | T 
+41-44-297 59 79 |
Netcetera AG | 8040 Z?rich | Switzerland | http://netcetera.com

On 29 Jul 2018, at 12:54, Massimo Manghi 
<massimo.man...@alice.it<mailto:massimo.man...@alice.it>> wrote:

Rivet's git repository is ready and available from

https://git-wip-us.apache.org/repos/asf/tcl-rivet.git

the repository is generated from the svn import but I selected only the 
branches that are currently existing in the svn repository. I haven't checked 
if all the project's committers have already been granted the right to push 
their commits.

If every thing is alright for you I will flag the infrastructure to switch the 
svn repository to read-only. Thus the code of websh and mod_tcl will be freezed 
in their current state.

Please: *I ask you to explicitly comment on this* before I go on with this step

-- Massimo

$ git tag
2.0.0
2.0.1
2.0.2
2.0.3
2.0.4
2.0.5
2.0.6
2.1.0
2.1.1
2.1.2
2.1.3
2.1.4
2.2.0
2.2.1
2.2.2
2.2.3
2.2.4
2.3.0
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
3.0.0
3.0.1
3.0.2

$ git branch -r
 origin/1_0
 origin/2.0
 origin/2.1
 origin/2.2
 origin/2.3
 origin/3.0
 origin/HEAD -> origin/master
 origin/apreq-multipart
 origin/master


---------------------------------------------------------------------
To unsubscribe, e-mail: 
rivet-dev-unsubscr...@tcl.apache.org<mailto:rivet-dev-unsubscr...@tcl.apache.org>
For additional commands, e-mail: 
rivet-dev-h...@tcl.apache.org<mailto:rivet-dev-h...@tcl.apache.org>

Reply via email to