Hi Ronnie

I think we can have repositories created also for websh and mod_tcl. In fact we never moved them to some sort of attic. We just declared their development stopped and we don't have resources to resume it. The fact that Rivet is still active is an argument that Apache Tcl is active and we have a right to preserve the way we want our software.

svn2git does a job deeper that I expected creating in the local repository where the import takes place all the past branches (including the deleted ones). When you get to the point of pushing to the remote repository you have to select the branches you want to keep and it's something that needs some historical memory of the project

 -- M

On 07/29/2018 05:35 PM, Ronnie Brunner wrote:
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 | 
[email protected]<mailto:[email protected]> | T 
+41-44-297 59 79 |
Netcetera AG | 8040 Z?rich | Switzerland | http://netcetera.com

On 29 Jul 2018, at 12:54, Massimo Manghi 
<[email protected]<mailto:[email protected]>> 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



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to