public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jim Kingdon <kingdon@redhat.com>
To: tromey@cygnus.com
Cc: pedwards@jaj.com, overseers@sourceware.cygnus.com
Subject: Re: A patch for toplevel Makefile.in [and a gnatsweb problem]
Date: Fri, 24 Mar 2000 08:58:00 -0000	[thread overview]
Message-ID: <200003241657.LAA19186@devserv.devel.redhat.com> (raw)
Message-ID: <20000324085800.J8EsE7_VB7G5ivgKv2nVfr5CNEhJIhIVDo-RRFJ3PJs@z> (raw)
In-Reply-To: <200003241647.IAA13832@ferrule.cygnus.com>

> Note to other sourceware admins: we run a locally-patched gnatsweb.

I've added a note to
http://sourceware.cygnus.com/sourceware/gnats.html - I can be kind of
a packrat with respect to keeping around records like that (if people
find these things helpful, do try to keep them up to date or otherwise
help, it gets discouraging if such pages are suspected of being
write-only).

> I sent this patch to the gnatsweb maintainer

Excellent!  Thanks for doing this.

> but I have no idea if it was incorporated.

Well, if you can succeed in working with the maintainers, you might
have the potential to save yourself merging work in the future :-)
(yeah, I know, this message is shameless evangelising, but I'm not
above that at times).

  parent reply	other threads:[~2000-03-24  8:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Phil Edwards
2000-03-24  8:12 ` Phil Edwards
2000-12-30  6:08 ` Tom Tromey
2000-03-27 17:36   ` Tom Tromey
2000-12-30  6:08 ` Tom Tromey
2000-03-24  8:47   ` Tom Tromey
2000-12-30  6:08   ` Jim Kingdon [this message]
2000-03-24  8:58     ` Jim Kingdon
  -- strict thread matches above, loose matches on Subject: below --
2000-12-30  6:08 Phil Edwards
2000-03-21 13:39 ` Phil Edwards
2000-12-30  6:08 ` Tom Tromey
2000-03-21 14:16   ` Tom Tromey

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=200003241657.LAA19186@devserv.devel.redhat.com \
    --to=kingdon@redhat.com \
    --cc=overseers@sourceware.cygnus.com \
    --cc=pedwards@jaj.com \
    --cc=tromey@cygnus.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).