From: Mark Newman <markn_46@yahoo.com>
To: Jim Ingham <jingham@apple.com>, gdb@sources.redhat.com
Subject: Re: gdb Digest 7 Nov 2003 16:00:26 -0000 Issue 1325
Date: Fri, 07 Nov 2003 18:03:00 -0000 [thread overview]
Message-ID: <20031107180331.20521.qmail@web13801.mail.yahoo.com> (raw)
In-Reply-To: <3432BCBC-1148-11D8-8D8B-000A277A8808@apple.com>
JIm -
could you point us to your cvs?
In addition can you provide a pointer or whatever to
something that indicates that that code is not Apple
IP and does not contain any Apple or anyone else's IP?
Mark
--- Jim Ingham <jingham@apple.com> wrote:
> Elena,
>
> On Nov 7, 2003, at 8:00 AM,
> gdb-digest-help@sources.redhat.com wrote:
>
> > the objc support is in gdb mainline and it has
> been there for a while.
> > There are some bugs still, but it was merged.
> > Are you referring to something else?
>
> Yes, I was referring to the very beginnings of
> Adam's work. Since the
> tarball of the Apple sources were sitting on the FSF
> site, he naturally
> started from there. But since they had been sitting
> for a while, the
> first task he faced was reconciling the changes in
> the relevant areas
> of the tarball with the changes in the FSF sources
> between the time the
> tarball was dropped and when he got it. At that
> time, we were keeping
> pretty current with the FSF distro, so we had done
> this job already -
> and the results were readily available in our CVS
> repository. IIRC, we
> figured out what was going on pretty quickly and set
> him straight, but
> that is the sort of pointless duplication of effort
> that it would be
> good to avoid.
>
> >
> > Same story for the interpreter stuff which Keith,
> Andrew and I merged.
> >
>
> I am pretty sure Keith worked from our CVS
> repository, at least that is
> what I urged him to do. By the time you & Andrew
> got to it, I think
> the work was pretty far along, so you probably
> didn't have any need to
> refer to our version.
>
> > I think we went through this before, with the
> previoius tarball. If
> > it's too hard a requirement, then let's forget
> about it. We'll live
> > with the status quo.
>
> It is obviously not hard but I worry it is likely to
> be
> counter-productive. That was what we "went through
> before" and the
> event somewhat justified my concerns.
>
> Pointing folks at our CVS repository is much easier,
> and we even have
> anonymous access now for those who don't want to
> give out their e-mail
> addresses... Plus then they have all the benefits
> of CVS in trying to
> figure out why we did all the screwy things we
> did...
>
> Jim
>
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
> Jim Ingham
>
> jingham@apple.com
> Developer Tools - gdb
>
next prev parent reply other threads:[~2003-11-07 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1068220826.2391.ezmlm@sources.redhat.com>
2003-11-07 17:31 ` Jim Ingham
2003-11-07 18:03 ` Mark Newman [this message]
2003-11-07 19:16 ` Jim Ingham
2003-11-07 21:24 ` Mark Newman
2003-11-07 18:04 ` Elena Zannoni
2003-11-07 19:12 ` Jim Ingham
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=20031107180331.20521.qmail@web13801.mail.yahoo.com \
--to=markn_46@yahoo.com \
--cc=gdb@sources.redhat.com \
--cc=jingham@apple.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