public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jim Kingdon <kingdon@redhat.com>
To: cgf@cygnus.com
Cc: overseers@sourceware.cygnus.com
Subject: Re: creating new projects
Date: Sat, 30 Dec 2000 06:08:00 -0000	[thread overview]
Message-ID: <200003260123.UAA28811@devserv.devel.redhat.com> (raw)
In-Reply-To: <20000325193448.J802@cygnus.com>

> Has anyone (i.e., Jim K) heard any more about sourceware's fate?

It's the status quo.  Little/no official status (just like it has been
since it was started).  To a first approximation, that is how We
(there is no we) have wanted it.

WARNING: multiple messages have this Message-ID
From: Jim Kingdon <kingdon@redhat.com>
To: cgf@cygnus.com
Cc: overseers@sourceware.cygnus.com
Subject: Re: creating new projects
Date: Sat, 25 Mar 2000 17:23:00 -0000	[thread overview]
Message-ID: <200003260123.UAA28811@devserv.devel.redhat.com> (raw)
Message-ID: <20000325172300.u2PSvrDljJN6_nD2Vg4Zc4QZvHWi4Kw7tkZzzak7Q-Q@z> (raw)
In-Reply-To: <20000325193448.J802@cygnus.com>

> Has anyone (i.e., Jim K) heard any more about sourceware's fate?

It's the status quo.  Little/no official status (just like it has been
since it was started).  To a first approximation, that is how We
(there is no we) have wanted it.

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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Ben Elliston
2000-03-25  7:48 ` Ben Elliston
2000-12-30  6:08 ` Tom Tromey
2000-03-25  8:24   ` Tom Tromey
2000-12-30  6:08   ` Chris Faylor
2000-03-25 16:34     ` Chris Faylor
2000-12-30  6:08     ` Jim Kingdon [this message]
2000-03-25 17:23       ` Jim Kingdon
2000-12-30  6:08       ` Chris Faylor
2000-03-25 17:33         ` Chris Faylor
2000-12-30  6:08 ` Jim Kingdon
2000-03-25 17:45   ` Jim Kingdon
2000-12-30  6:08 ` Jeffrey A Law
2000-03-27 12:14   ` Jeffrey A Law

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=200003260123.UAA28811@devserv.devel.redhat.com \
    --to=kingdon@redhat.com \
    --cc=cgf@cygnus.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).