Re: What to do with github.com/apache/sling (was [git] Migration to git repositories sort of complete)

2017-10-25 Thread Robert Munteanu
On Mon, 2017-10-23 at 23:38 +0200, Robert Munteanu wrote: > 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'

Re: What to do with github.com/apache/sling (was [git] Migration to git repositories sort of complete)

2017-10-23 Thread Robert Munteanu
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

Re: What to do with github.com/apache/sling (was [git] Migration to git repositories sort of complete)

2017-10-23 Thread Ian Boston
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

Re: What to do with github.com/apache/sling (was [git] Migration to git repositories sort of complete)

2017-10-23 Thread Robert Munteanu
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 >

Re: What to do with github.com/apache/sling (was [git] Migration to git repositories sort of complete)

2017-10-22 Thread Ian Boston
Hi, Good solution. One small modification to help anyone get to the old tree. 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"

Re: What to do with github.com/apache/sling (was [git] Migration to git repositories sort of complete)

2017-10-22 Thread Justin Edelson
+1 Great solution. On Sat, Oct 21, 2017 at 3:26 PM Robert Munteanu wrote: > On Fri, 2017-10-20 at 23:19 +0200, Robert Munteanu wrote: > > I guess the 'minimal damage' approach would be to switch the main > > branch and make that empty, with just a README.md . > > > > Would

Re: What to do with github.com/apache/sling (was [git] Migration to git repositories sort of complete)

2017-10-21 Thread Robert Munteanu
On Fri, 2017-10-20 at 23:19 +0200, Robert Munteanu wrote: > I guess the 'minimal damage' approach would be to switch the main > branch and make that empty, with just a README.md . > > Would need to talk to infra to see how that can happen. Unless anyone > is opposed, I would create a branch

Re: What to do with github.com/apache/sling (was [git] Migration to git repositories sort of complete)

2017-10-21 Thread Robert Munteanu
I guess the 'minimal damage' approach would be to switch the main branch and make that empty, with just a README.md . Would need to talk to infra to see how that can happen. Unless anyone is opposed, I would create a branch called 'archived' with the following README.md contents:

Re: What to do with github.com/apache/sling (was [git] Migration to git repositories sort of complete)

2017-10-20 Thread Ian Boston
Hi, I can think of at least one non public Jira whose links will break. Archiving probably wont work as most links point to a line number, commit, or something specific. I guess we could just say tough, its too much effort to fix, anyone really interested will find the information for themselves.