Guten Tag Roland Uuesoo,
am Donnerstag, 2. März 2017 um 13:06 schrieben Sie:

> When migrating to GIT, the commit history is retained, there is no
> point keeping the old SVN repository.

Of course there might be a point, e.g. for people using svn:externals
to integrate log4cxx into their project. This is a quite common setup
and would keep working if the old code base would be kept e.g.
read-only or would be mirrored or whatever.

On the other hand, the Apache GIT-repos are mirrored to GitHub and
GitHub provides a SVN bridge. So one could really delete the sources
from the SVN and people seeing things failing could be advised to use
the GitHub SVN-bridge instead. I'm doing that already for e.g. Apache
Wicket and it somewhat works, currently even better than some months
ago, where I often faced timeouts I didn't face with "native" GitHub
repos and their SVN-bridge.

That's why Im asking, one simply needs to know/decide. I could
perfectly live with the second approach.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail: thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

Reply via email to