From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: nathan@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: GNATS web
Date: Mon, 03 Jul 2000 15:31:00 -0000 [thread overview]
Message-ID: <200007032220.AAA01113@loewis.home.cs.tu-berlin.de> (raw)
In-Reply-To: <39608A3A.CEC5C99F@codesourcery.com>
> The generic query feature of gnatsweb gives bug reports in descending order.
> The execute saved query feature gives them in ascending order.
>
> This is annoying ...
> I have a mild preference for descending order.
I believe this is entirely done in
wwwdocs/gnatsweb/cgi-bin.pl:by_field, which in turn is made available
through the table headers (and could be entered into the URL by
adding, say, &sortby=Class).
I'm not a perl hacker, so again, anybody willing to contribute is
encouraged to do so. The easiest thing may be to add new sortby
criteria: PRR, CategoryR, etc, and put appropriate links into the
table headers. If anybody wants to tackle this, allowing to specify
the sort order in the query may be also useful.
Regards,
Martin
prev parent reply other threads:[~2000-07-03 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-03 5:40 Nathan Sidwell
2000-07-03 15:31 ` Martin v. Loewis [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200007032220.AAA01113@loewis.home.cs.tu-berlin.de \
--to=martin@loewis.home.cs.tu-berlin.de \
--cc=gcc@gcc.gnu.org \
--cc=nathan@codesourcery.com \
/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.
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).