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' bran
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 disadva
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 impressi
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
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"
+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 need to talk to infra
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 called
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:
8<--
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.
Hi Ian,
On Fri, 2017-10-20 at 11:04 +0100, Ian Boston wrote:
> BTW,
> Deleting github:apache/sling will 404 every reference to code there
> from
> JIRA in many places. Probably not a good idea to delete it, but it
> should
> be made readonly.
That's a good point, I did not consider this.
The pr
10 matches
Mail list logo