sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Munteanu <romb...@apache.org>
Subject Re: What to do with github.com/apache/sling (was [git] Migration to git repositories sort of complete)
Date Mon, 23 Oct 2017 21:38:44 GMT
On Mon, 2017-10-23 at 18:40 +0100, Ian Boston wrote:
> > 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/

That's pretty cool. I would assume that we won't be able to reclaim the
old 'sling' name, otherwise the redirects would not work, but this
should make it even clearer.

Robert

Mime
View raw message