public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jason Molenda <crash@cygnus.com>
To: Tom Tromey <tromey@cygnus.com>
Cc: Overseers List <overseers@sourceware.cygnus.com>
Subject: Re: FOM for everybody ?
Date: Sat, 30 Dec 2000 06:08:00 -0000	[thread overview]
Message-ID: <20000213143223.A23399@cygnus.com> (raw)
In-Reply-To: <200002132228.OAA07394@ferrule.cygnus.com>

On Sun, Feb 13, 2000 at 02:28:19PM -0800, Tom Tromey wrote:

> I could hack FOM if you'd rather I do that.
> That has its own drawbacks, namely maintaining a hacked version.
> My reading of the code is that this would be rather easy to do, though.
> 
> A third option is to write a patch and send it to the FOM maintainer,
> and decide what to do depending on whether he accepts it.

I don't like to hack the sources if we can avoid it--just makes things
more difficult for follow-on maintainers.  If all n copies of the fom.cgi
are identical, or nearly so, then we can scriptily autogenerate/autoupdate
all the copies of them and ignore the hackiness of it.

BTW I'll be working all day long on sourceware stuff, so if you want we
can probably throw this all together within the day.  

Jason

  reply	other threads:[~2000-12-30  6:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Tom Tromey
2000-12-30  6:08 ` Jason Molenda
2000-12-30  6:08   ` Tom Tromey
2000-12-30  6:08     ` Jason Molenda [this message]
2000-12-30  6:08 ` Jeffrey A Law
2000-12-30  6:08   ` Tom Tromey
2000-12-30  6:08   ` Jim Kingdon
2000-12-30  6:08     ` Jeffrey A Law
2000-12-30  6:08       ` Jim Kingdon
2000-12-30  6:08         ` Jason Molenda
2000-12-30  6:08     ` Tom Tromey
2000-12-30  6:08       ` Someone

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=20000213143223.A23399@cygnus.com \
    --to=crash@cygnus.com \
    --cc=overseers@sourceware.cygnus.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).