all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: 8257@debbugs.gnu.org, rgm@gnu.org
Cc: 8257-done@debbugs.gnu.org
Subject: bug#8257: Links to browse source code broken
Date: Tue, 15 Mar 2011 21:11:13 +0100	[thread overview]
Message-ID: <AANLkTikeuiCw1RZ=Mwx837SzCrqLtRcdJX-9Huti2yW4@mail.gmail.com> (raw)
In-Reply-To: <19839.44673.488476.877911@fencepost.gnu.org>

On Tue, Mar 15, 2011 at 7:22 PM, Glenn Morris <rgm@gnu.org> wrote:
>
> Lennart Borgman wrote (on Tue, 15 Mar 2011 at 14:25 +0100):
>
>> Then link on
>>
>>    emacs - Summary [Savannah]
>>    http://savannah.gnu.org/projects/emacs/
>>
>> in the menus
>>
>>    Source Code / Browse Sources Repository
>
> There are 3 such links.
> The git one works. The CVS one works. The bzr one takes to you a page
> that says:
>
>  loggerhead disabled due to instability; if you're interesting in
>  maintaining it, please check http://savannah.gnu.org/maintenance/Bzr

This is not what Chrome shows. It justs says:

  Oops! This link appears to be broken.
  Suggestions:
   Access a cached copy of bzr.­savannah.­gnu.­org/­lh/­emacs
   Go to gnu.­org
   ...

I tested on my own site and it looks just as I expect for 404 pages.

I also tested with Opera and indeed there I can see the message you
suggested should be there.

It still looks to me something is broken with the link I mentioned.





  reply	other threads:[~2011-03-15 20:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 13:25 bug#8257: Links to browse source code broken Lennart Borgman
2011-03-15 18:22 ` Glenn Morris
2011-03-15 20:11   ` Lennart Borgman [this message]
2011-03-15 20:42     ` Glenn Morris
2011-03-15 20:43       ` Lennart Borgman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTikeuiCw1RZ=Mwx837SzCrqLtRcdJX-9Huti2yW4@mail.gmail.com' \
    --to=lennart.borgman@gmail.com \
    --cc=8257-done@debbugs.gnu.org \
    --cc=8257@debbugs.gnu.org \
    --cc=rgm@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.