From: Jason Molenda <jmolenda@apple.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: binutils@sources.redhat.com, Stan Shebs <shebs@apple.com>,
gdb@sources.redhat.com
Subject: Re: Retire the MPW support from toplevel and binutils
Date: Thu, 25 Mar 2004 22:37:00 -0000 [thread overview]
Message-ID: <D3C75D2C-7E96-11D8-9E08-000393D457E2@apple.com> (raw)
In-Reply-To: <4062FB6D.5060108@gnu.org>
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.
If the modules file is not updated, every checkout until the end of
time will include
cvs checkout: warning: src/mpw-build.in is not (any longer) pertinent
cvs checkout: warning: src/mpw-README is not (any longer) pertinent
cvs checkout: warning: src/mpw-config.in is not (any longer) pertinent
cvs checkout: warning: src/mpw-configure is not (any longer) pertinent
cvs checkout: warning: src/mpw-install is not (any longer) pertinent
Which do you think is going to cause more questions and confusion:
People checking out binutils 2.10 from CVS and being shocked that the
mpw support files, which no longer do anything useful, are not present,
or people checking out TOT and wondering what the heck these five
missing files are and why they're not pertinent.
The modules file must be updated.
J
next prev parent reply other threads:[~2004-03-25 19:59 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 [this message]
2004-03-25 23:02 ` Andrew Cagney
2004-03-26 1:07 ` Stan Shebs
2004-03-26 6:11 ` Andrew Cagney
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=D3C75D2C-7E96-11D8-9E08-000393D457E2@apple.com \
--to=jmolenda@apple.com \
--cc=binutils@sources.redhat.com \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.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).