public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Stan Shebs <shebs@apple.com>
Cc: Jason Molenda <jmolenda@apple.com>,
	binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: Retire the MPW support from toplevel and binutils
Date: Fri, 26 Mar 2004 06:11:00 -0000	[thread overview]
Message-ID: <40635C52.5020102@gnu.org> (raw)
In-Reply-To: <4063585E.9090101@apple.com>

> Andrew Cagney wrote:
> 
>>> On Mar 25, 2004, at 7:31 AM, Andrew Cagney wrote:
>>>
>>>>> I'm sure you already knew this, but you'll need to update the cvs modules for the repository at the same time you're doing this - these files are explicitly named in there:
>>>>
>>>>
>>>>
>>>>
>>>> Er, the modules file should _not_ be updated.  You can always add, but never remove entries.
>>>
>>>
>>>
>>>
>>> In this case, these support files have been obsolete for longer than the sourceware repositories have been live.  From a completely maniacal outlook we'd never want to remove files like this, but looking at it realistically, there's nothing being lost here.  Yes, if someone checks out binutils 2.10 (one of the first releases after the repositories moved to sourceware, circa June 2000) by a cvs command they'll be missing the mpw support files from the top level.
>>
>>
>>
>> On the other hand this will cause them to mysteriously disappear from the current live GDB and BINUTILS branches.
>>
>> Anyway to sit on this until after there's been a release pulled from those branches?
> 
> 
> Well, they're not any different from what was in any of the last
> releases. In fact, those files haven't been touched (except for
> a couple mass-edits) since I last worked on them, in 1996. So on
> the off chance that some software archaeologist wants to get a
> PhD studying the mysteries of Mac in GNU (hey, it could happen!),
> there will be plenty of releases where the latest versions may
> be found.

Stan, what's the urgency?  Why not wait until GDB 6.1 and BINUTILS 1.? 
are released as that is obviously going to make everyones life easier. 
What's that, a few extra weeks?

BTW, I've a few modules of my own that should be dropped.  If we do them 
all in a single hit and when those branches have died, things will work 
a lot better.

Andrew


  reply	other threads:[~2004-03-25 22:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25 13:38 Stan Shebs
2004-03-25 13:39 ` Ian Lance Taylor
2004-03-25 13:55 ` Jason Molenda
2004-03-25 14:30   ` Stan Shebs
2004-03-25 19:59   ` Andrew Cagney
2004-03-25 22:22     ` Ian Lance Taylor
2004-03-25 22:37     ` Jason Molenda
2004-03-25 23:02       ` Andrew Cagney
2004-03-26  1:07         ` Stan Shebs
2004-03-26  6:11           ` Andrew Cagney [this message]
2004-03-26  9:10             ` Stan Shebs
2004-03-26 13:34               ` Andrew Cagney
2004-04-02 16:25               ` Andrew Cagney
2004-04-02 16:40                 ` Daniel Jacobowitz
2004-04-02 19:12                 ` Stan Shebs
2004-04-03  5:47                   ` Objcopy alignment Dave Murphy

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=40635C52.5020102@gnu.org \
    --to=cagney@gnu.org \
    --cc=binutils@sources.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jmolenda@apple.com \
    --cc=shebs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).