From: Giorgos Keramidas <keramida@ceid.upatras.gr>
To: Jason Rumney <jasonr@f2s.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Drew Adams <drew.adams@oracle.com>,
emacs-devel@gnu.org
Subject: Re: document the bug-tracker Web site?
Date: Sun, 21 Dec 2008 05:25:03 +0200 [thread overview]
Message-ID: <874p0yky5s.fsf@kobe.laptop> (raw)
In-Reply-To: <494DAF5D.9060905@f2s.com> (Jason Rumney's message of "Sun, 21 Dec 2008 10:52:13 +0800")
On Sun, 21 Dec 2008 10:52:13 +0800, Jason Rumney <jasonr@f2s.com> wrote:
> Stefan Monnier wrote:
>> I don't see why we should wait. We use it right now, so it's "the real
>> thing". When we move it elsewhere (or switch to some other tool), we
>> will need to update the page correspondingly.
>
> So we end up with versions of the manuals out there with an obsolete
> bug database site address, which we knew in advance would happen
> before we released those manuals.
>
> Can we ask the FSF admins to set up a redirection now from say
> http://www.gnu.org/software/emacs/bugs to the current bug database,
> then when we move it to gnu.org, we need only change the redirection,
> and the existing manuals will remain accurate.
The time window between the release of Emacs 23.1 and the release of
24.1 may be slightly large. So I think it makes sense to have some way
to avoid links in the manual that are going to be obsolete when the move
happens.
Setting up the redirection now and using the www.gnu.org link is a good
way of avoiding the problem of an obsolete link in the manual :)
next prev parent reply other threads:[~2008-12-21 3:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 17:24 document the bug-tracker Web site? Drew Adams
2008-12-20 3:37 ` Jason Rumney
2008-12-21 2:02 ` Stefan Monnier
2008-12-21 2:52 ` Jason Rumney
2008-12-21 3:25 ` Giorgos Keramidas [this message]
2008-12-21 4:17 ` Stefan Monnier
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=874p0yky5s.fsf@kobe.laptop \
--to=keramida@ceid.upatras.gr \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@f2s.com \
--cc=monnier@iro.umontreal.ca \
/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.