public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Yngve Svendsen <yngve.svendsen@clustra.com>
Cc: <gnats-devel@sources.redhat.com>
Subject: Re: Gnatsweb: patch to add stylesheet support
Date: Wed, 21 Mar 2001 01:15:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.33.0103211002140.98416-100000@deneb.dbai.tuwien.ac.at> (raw)
In-Reply-To: <5.1.0.10.2.20010320134013.00bb6d08@mail.trd.clustra.com>

On Tue, 20 Mar 2001, Yngve Svendsen wrote:
> The following patch adds the ability to have an external stylesheet linked
> to all pages generated by Gnatsweb. It is against the version in the
> current GNATS 4 CVS.

That patch did not apply automatically (it seems your mailer lost
spaces?), but I added it manually. Thanks for the patch!

Note that we also need ChangeLog entries for patches. I wrote the
following for you this time, though it'd be great could you supply
them in the future.

  2001-03-21  Yngve Svendsen  <yngve.svendsen@clustra.com>

        * gnatsweb.pl: New configuration variable $site_stylesheet.
        (page_start_html): Use it.

> Gerald: Isn't it a good idea to change the version number of the
> development Gnatsweb in CVS to distinguish it from the version that works
> with GNATS 3.x? I would suggest going to "4.0-dev". In the future, version
> numbers don't need to be synced between GNATS and Gnatsweb, but I think it
> is a good idea to use a common starting point for version 4, since older
> versions of Gnatsweb won't work with GNATS 4. Does that make sense?

Yes, a lot of sense, though I'd prefer 3.95, which also leaves a bit of
room for signifcant bumps before 4.0 in case we need that.

I installed the following:

  2001-03-21  Gerald Pfeifer  <pfeifer@dbai.tuwien.ac.at>

        * gnatsweb.pl ($VERSION): Bump to 3.95.

> Next, I'll be going through some of the HTML constructs produced by
> Gnatsweb in order to make them more amenable to formatting with
> stylesheets. Expect more patches soon.

Great. In that case I'd like to give you CVS write access and preapprove
these changes (that is, you can go ahead and commit them w/o any further
approval), especially as I'll be out-of-town and offline for about two
weeks starting next weekend.

Please contact me privately for details!

Also, if you're interested in fixing the HTML output of gnatsweb,
you  might want to have a look at the bug report at
< http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=961&database=gcc >

Thanks for your contributions!
Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

      reply	other threads:[~2001-03-21  1:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-20  4:48 Yngve Svendsen
2001-03-21  1:15 ` Gerald Pfeifer [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=Pine.BSF.4.33.0103211002140.98416-100000@deneb.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=gnats-devel@sources.redhat.com \
    --cc=yngve.svendsen@clustra.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).