From: Tom Lord <lord@emf.net>
To: gcc@gcc.gnu.org
Subject: Re: source mgt....[_HAS_ gcc relevance]
Date: Mon, 16 Dec 2002 04:40:00 -0000 [thread overview]
Message-ID: <200212161126.DAA07012@emf.net> (raw)
In-Reply-To: <200212161105.DAA06401@emf.net> (message from Tom Lord on Mon, 16 Dec 2002 03:05:51 -0800 (PST))
me:
> Yeah, I said it badly. Observing gcc, Mark makes lots of
> judgment calls and sets focus and picks dates and things like
> that.
And even there, maybe said it badly again. I'm really not trying to
sell Mark short. "Generally keeps on top of things in gcc
developement (no small task)" might be a better description -- i.e.,
not just throwing darts at a calendar and so forth.
-t
next prev parent reply other threads:[~2002-12-16 11:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 3:05 Robert Dewar
2002-12-16 4:15 ` Tom Lord
2002-12-16 4:40 ` Tom Lord [this message]
2002-12-16 16:36 ` Florian Weimer
2002-12-17 0:38 ` Momchil Velikov
2002-12-17 11:41 ` Daniel Egger
2002-12-17 13:17 ` Tom Lord
-- strict thread matches above, loose matches on Subject: below --
2002-12-18 11:03 Robert Dewar
2002-12-16 4:56 Richard Kenner
2002-12-16 5:33 ` Tom Lord
2002-12-14 21:34 source mgt. requirements solicitation Linus Torvalds
2002-12-14 23:12 ` source mgt....[_HAS_ gcc relevance] Tom Lord
2002-12-14 22:12 ` Linus Torvalds
2002-12-15 3:04 ` Zack Weinberg
2002-12-15 3:23 ` Tom Lord
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=200212161126.DAA07012@emf.net \
--to=lord@emf.net \
--cc=gcc@gcc.gnu.org \
/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).