From: Jason Molenda <jmolenda@apple.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: Mark Newman <markn_46@yahoo.com>, Jim Ingham <jingham@apple.com>,
gdb@sources.redhat.com
Subject: Re: Apple's async changes
Date: Fri, 05 Dec 2003 20:34:00 -0000 [thread overview]
Message-ID: <4FE5663F-2762-11D8-9FBF-000393D457E2@apple.com> (raw)
In-Reply-To: <3FD0DA86.8070001@gnu.org>
That's absurd -- I think you're the only one concerned about the fact
that we haven't tarred up our sources on some given date and uploaded
them to an ftp server. Is it the statement that you want? Like the
one I wrote when I tarred up the sources and uploaded them to the ftp
server a while back? I can write another one saying "Yeah, it's all
for the FSF, please anyone who wants to use any of that code, do it,"
if that makes a difference in your mind. No one in the Apple developer
tools department -- up through our VP -- wants anything but to
contribute this code to the FSF source bases.
The async code in the last Apple drop and the async code in the Apple
CVS repo are very nearly identical - we got that working long ago, and
we only fix an occasional bug a couple times a year.
J
On Dec 5, 2003, at 11:20 AM, Andrew Cagney wrote:
>> What are the problems using the Apple CVS?
>
> People are more comfortable (and feel that they are on safer legal
> ground) if they take change from a work that Apple has clearly and
> publically contributed to and been accepted by the FSF.
>
> Andrew
>
>
next prev parent reply other threads:[~2003-12-05 20:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 23:17 Mark Newman
2003-12-05 17:56 ` Mark Newman
2003-12-05 17:58 ` Jim Ingham
2003-12-05 19:20 ` Andrew Cagney
2003-12-05 20:34 ` Jason Molenda [this message]
2003-12-05 21:08 ` Andrew Cagney
2003-12-05 20:49 ` Jason Molenda
2003-12-05 22:25 ` Mark Newman
2003-12-06 1:43 ` Daniel Berlin
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=4FE5663F-2762-11D8-9FBF-000393D457E2@apple.com \
--to=jmolenda@apple.com \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jingham@apple.com \
--cc=markn_46@yahoo.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