public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@cygnus.com>
To: Jim Kingdon <kingdon@redhat.com>
Cc: cgf@cygnus.com, jlarmour@redhat.co.uk, overseers@sourceware.cygnus.com
Subject: Re: ORBS redux, round n
Date: Sat, 30 Dec 2000 06:08:00 -0000	[thread overview]
Message-ID: <200003241650.IAA13835@ferrule.cygnus.com> (raw)
In-Reply-To: <200003241641.LAA18292@devserv.devel.redhat.com>

Jim> Any objections to adding Jonathan Larmour, and I guess other
Jim> project maintainers who ask?

It is fine with me.

Jim> I guess I'd plan on applying some small amount of discretion, but
Jim> if there is some big hidden cost to putting people in this group,
Jim> let me know.

As long as we remind people we add to this group that they should be
careful, it'll be fine.

T

WARNING: multiple messages have this Message-ID
From: Tom Tromey <tromey@cygnus.com>
To: Jim Kingdon <kingdon@redhat.com>
Cc: cgf@cygnus.com, jlarmour@redhat.co.uk, overseers@sourceware.cygnus.com
Subject: Re: ORBS redux, round n
Date: Fri, 24 Mar 2000 08:50:00 -0000	[thread overview]
Message-ID: <200003241650.IAA13835@ferrule.cygnus.com> (raw)
Message-ID: <20000324085000.e2JWB4owkPzijyMr-u06xxLSgpNGmW5K_rhi-P7EYVo@z> (raw)
In-Reply-To: <200003241641.LAA18292@devserv.devel.redhat.com>

Jim> Any objections to adding Jonathan Larmour, and I guess other
Jim> project maintainers who ask?

It is fine with me.

Jim> I guess I'd plan on applying some small amount of discretion, but
Jim> if there is some big hidden cost to putting people in this group,
Jim> let me know.

As long as we remind people we add to this group that they should be
careful, it'll be fine.

T

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

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Jim Kingdon
2000-03-24  8:22 ` Jim Kingdon
2000-12-30  6:08 ` Chris Faylor
2000-03-24  8:28   ` Chris Faylor
2000-12-30  6:08   ` Jonathan Larmour
2000-03-24  8:32     ` Jonathan Larmour
2000-12-30  6:08     ` Chris Faylor
2000-03-24  8:33       ` Chris Faylor
2000-12-30  6:08       ` Jim Kingdon
2000-03-24  8:41         ` Jim Kingdon
2000-12-30  6:08         ` Jonathan Larmour
2000-03-24  8:54           ` Jonathan Larmour
2000-12-30  6:08           ` Jeffrey A Law
2000-03-24  9:19             ` Jeffrey A Law
2000-12-30  6:08             ` Jonathan Larmour
2000-03-24  9:22               ` Jonathan Larmour
2000-12-30  6:08               ` Chris Faylor
2000-03-24  9:57                 ` Chris Faylor
2000-12-30  6:08           ` Chris Faylor
2000-03-24  8:58             ` Chris Faylor
2000-12-30  6:08             ` Chris Faylor
2000-03-24  9:02               ` Chris Faylor
2000-12-30  6:08               ` Jim Kingdon
2000-03-24  9:54                 ` Jim Kingdon
2000-12-30  6:08         ` Tom Tromey [this message]
2000-03-24  8:50           ` Tom Tromey
2000-12-30  6:08           ` Chris Faylor
2000-03-24  8:53             ` Chris Faylor
2000-12-30  6:08         ` Jeffrey A Law
2000-03-24  9:11           ` Jeffrey A Law
  -- strict thread matches above, loose matches on Subject: below --
2000-12-30  6:08 Phil Edwards
2000-03-24  9:04 ` Phil Edwards

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=200003241650.IAA13835@ferrule.cygnus.com \
    --to=tromey@cygnus.com \
    --cc=cgf@cygnus.com \
    --cc=jlarmour@redhat.co.uk \
    --cc=kingdon@redhat.com \
    --cc=overseers@sourceware.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).