Hi > So that would mean that all link to trunk would result in a 404 Not > Found, as I have tried it with [1].
> So we either > a) break all links to the 'trunk' branch, or > b) leave the 'trunk' branch alive, with the added disadvantage that > navigating from a 'trunk' link leaves the impression that the > branch/repo are still in use. > Did I get this right or is there something else? yes. a) isnt very friendly. If we choose b) we could rename the repository to sling-svn-ending-2017-10 or something like that. GitHub will redirect all traffic. https://help.github.com/articles/renaming-a-repository/ The other option is to transfer ownership of the repository. Git will also redirect. https://help.github.com/articles/about-repository-transfers/ Best Regards Ian On 23 October 2017 at 13:48, Robert Munteanu <[email protected]> wrote: > On Sun, 2017-10-22 at 15:28 +0100, Ian Boston wrote: > > Hi, > > Good solution. One small modification to help anyone get to the old > > tree. > > Well, I saw what we did at Adobe last time we had something similar :-) > > > > > Rather than switching the main branch and making it empty, if you > > branch > > trunk to a new branch "archive" and then make trunk empty as you > > suggest, > > it will be possible to point anyone who gets a 404 to the new > > "archive" > > branch. Tagging the last commit from SVN would also help keep a > > permanent > > record. > > > > Only those URLs that are not pointing to a commit/tag/branch (other > > than > > trunk) will be broken and the README left in trunk can explain how to > > change the URL. > > I think that there are plenty of links pointing to 'trunk' though. I > have tried to make permanent links to github, but I did not do that all > the time. > > So that would mean that all link to trunk would result in a 404 Not > Found, as I have tried it with [1]. > > So we either > > a) break all links to the 'trunk' branch, or > b) leave the 'trunk' branch alive, with the added disadvantage that > navigating from a 'trunk' link leaves the impression that the > branch/repo are still in use. > > Did I get this right or is there something else? > > Robert > > [1]: https://github.com/apache/sling/blob/archived/KEYS >
