From: Jeffrey A Law <law@cygnus.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: pcg@goof.com, egcs@cygnus.com
Subject: Re: egcs, -W -Wall on by default during bootstrap (?)
Date: Sun, 08 Feb 1998 00:48:00 -0000 [thread overview]
Message-ID: <10784.886927543@hurl.cygnus.com> (raw)
In-Reply-To: <199802072023.PAA12901@caip.rutgers.edu>
In message < 199802072023.PAA12901@caip.rutgers.edu >you write:
> I'd much rather you choose for yourself what share you want to
> contribute and just let us know what you're working on so we don't
> duplicate work. But if more people start volunteering, I guess I'll
> have to coordinate. A good way to break it down yourself is to either
> say "I'll do all warnings in file X", or, "I'll do all warnings of type Y".
I think this is definitely the easiest way to break this down. File by
file. Or one backend at a time.
jeff
next prev parent reply other threads:[~1998-02-08 0:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-07 12:23 Kaveh R. Ghazi
1998-02-08 0:48 ` Jeffrey A Law [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-02-11 11:23 Kaveh R. Ghazi
1998-02-12 1:55 ` Jeffrey A Law
1998-02-04 13:19 Kaveh R. Ghazi
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=10784.886927543@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=ghazi@caip.rutgers.edu \
--cc=pcg@goof.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).