Hi Philippe, I did not say it was the optimal solution - but what brings the most value? - live working code or broken unmaintained artefacts of yesteryear?
I have migrated a lot of Subversion repos to Github, some were in an almost unmigratable state, due to bad decisions on repository layout and gitpan saved these distributions and I could get back to active maintenance instead of spending all my time trying to salvage history of old bug fixes. The changes file and distribution release history provided sufficient information to keep me happy and still draw the same picture of what was released to the public via CPAN. If possible, migrate - if time or other circumstances block - gitpan is an alternative solution. Happy New Year :-) jonasbn -- Twitter: @jonasbn > Den 4. jan. 2016 kl. 22.41 skrev Philippe Bruhat (BooK) > <philippe.bru...@free.fr>: > >> On Mon, Jan 04, 2016 at 07:21:01PM +0100, Jonas Brømsø Nielsen wrote: >> Hi Shlomi, >> >> A sane alternative to Subversion migration could be starting out from gitpan: >> >> https://github.com/gitpan/File-Remove <https://github.com/gitpan/File-Remove> > > But that replaces the full history with the history of whatever was released. > > -- > Philippe Bruhat (BooK) > > Eliminate a problem before it eliminates you! > (Moral from Groo The Wanderer #65 (Epic))
