From: "Ram Munjuluri" <rambabu@mindspring.com>
To: <pthreads-win32@sourceware.cygnus.com>
Subject: un-subscribe
Date: Fri, 14 Jul 2000 18:38:00 -0000 [thread overview]
Message-ID: <000901bfedfd$18230400$0a09010a@rambabu.com> (raw)
In-Reply-To: <396E75B7.9D00FEE4@ise.canberra.edu.au>
----- Original Message -----
From: Ross Johnson <rpj@ise.canberra.edu.au>
To: <pthreads-win32@sourceware.cygnus.com>
Sent: Thursday, July 13, 2000 10:06 PM
Subject: Re: Project Coordination
> Ross Johnson wrote:
> >
> > Dear all,
> >
> > This is a call for someone to take over as maintainer of
> > the Pthreads-Win32 project.
> >
> > There has not been a new release in 7 months even though
> > a number (but not an overwhelming number) of patches and
> > additions have been contributed during that time. The
> > current source tree is kept on sourceware.cygnus.com
> > although there is no requirement to keep it there.
>
> Ok, I accidently managed to post this prematurely. I was just
> going to add that I think the project needs someone who has
> more enthusiasm and expertise to put into it than I.
>
> My interest in the project was to learn about pthreads and
> get some idea of the Win32 API. That initial interest has been
> satisfied and I now have other interests that I've been
> persuing.
>
> The project seems to have been quite successful thanks to the
> quality of the contributed code. It needs someone with
> the core interest to keep those candles burning.
>
> I have a bunch of email from people who have sent in patches
> (although I may have lost a few in a disk crash around january).
> I also have some complete source trees for building with
> Borland (from different contributors). I will upload these
> and the email to the ftp site in the next few days.
>
> Ross
prev parent reply other threads:[~2000-07-14 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-13 18:46 Project Coordination Ross Johnson
2000-07-13 19:07 ` Ross Johnson
2000-07-14 18:38 ` Ram Munjuluri [this message]
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='000901bfedfd$18230400$0a09010a@rambabu.com' \
--to=rambabu@mindspring.com \
--cc=pthreads-win32@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).