unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Paul Pogonyshev <pogonyshev@gmx.net>
Cc: 5632@debbugs.gnu.org
Subject: bug#5632: header flood on individual bug HTML pages
Date: Tue, 23 Feb 2010 13:29:27 -0500	[thread overview]
Message-ID: <x2mxyz6c1k.fsf_-_@fencepost.gnu.org> (raw)
In-Reply-To: <201002232000.08207.pogonyshev@gmx.net> (Paul Pogonyshev's message of "Tue\, 23 Feb 2010 20\:00\:07 +0200")

Paul Pogonyshev wrote:

> Then how about linking such pages from
> http://debbugs.gnu.org/db/ix/full.html (found on

I have though about this, but I don't want to mix the two types of
pages in this way.

> http://debbugs.gnu.org/ section 'Viewing Bug Reports')?
> Alternatively, if there is a similar dynamic overview page, maybe
> debbugs.gnu.org main page should link to it?

Immediately under the above link, find links:

    Dynamic indices (updated on demand):

      * Packages with active and archived bug reports. 

Click active, then if you were to click "emacs" you would get a
dynamic list of all emacs bugs with nice formatting. However, there
are ~ 2000 bugs, which will take a long time to list, if the server
can even manage it. The static pages only really exist for this case.
If you do any kind of search, you get the nicely formatted pages in
the results.






      reply	other threads:[~2010-02-23 18:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-23 14:16 bug#5632: header flood on individual bug HTML pages Paul Pogonyshev
2010-02-23 16:56 ` Glenn Morris
     [not found] ` <handler.5632.D5632.126694420517378.notifdone@debbugs.gnu.org>
2010-02-23 18:00   ` bug#5632: closed by Glenn Morris <rgm@gnu.org> (Re: bug#5632: header flood on individual bug HTML pages) Paul Pogonyshev
2010-02-23 18:29     ` Glenn Morris [this message]

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=x2mxyz6c1k.fsf_-_@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=5632@debbugs.gnu.org \
    --cc=pogonyshev@gmx.net \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).