From: Ian Lance Taylor <ian@wasabisystems.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: Jason Molenda <jmolenda@apple.com>, Stan Shebs <shebs@apple.com>,
binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: Retire the MPW support from toplevel and binutils
Date: Thu, 25 Mar 2004 21:43:00 -0000 [thread overview]
Message-ID: <m3brmkc433.fsf@gossamer.airs.com> (raw)
In-Reply-To: <4062FB6D.5060108@gnu.org>
Andrew Cagney <cagney@gnu.org> writes:
> > 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:
> > src-support -a src/.cvsignore src/COPYING src/COPYING.LIB
> > src/COPYING.NEWLIB
> > src/COPYING.LIBGLOSS src/ChangeLog src/MAINTAINERS
> > src/Makefile.def src/Makefile.in src/Makefile.tpl src/README
> > src/README-maintainer-mode src/config src/config-ml.in
> > src/config.guess src/config.if src/config.sub src/configure
> > src/configure.in src/contrib src/etc src/gettext.m4 src/install-sh
> > src/libtool.m4 src/ltcf-c.sh src/ltcf-cxx.sh src/ltcf-gcj.sh
> > src/ltconfig src/ltmain.sh src/makefile.vms src/missing src/mkdep
> > src/mkinstalldirs src/move-if-change src/mpw-README
> > src/mpw-build.in src/mpw-config.in src/mpw-configure
> > src/mpw-install src/setup.com src/src-release src/symlink-tree
> > src/ylwrap
>
> Er, the modules file should _not_ be updated. You can always add, but
> never remove entries.
If leaving the files in there doesn't cause any errors or warnings
when doing a checkout, then I agree that the modules file should not
be changed.
However, if we do get errors or warnings, then I'm afraid that we must
change it, even though it is clearly the wrong thing to do from a
version control standpoint. The modules file in general is a bug in
CVS, not a feature. It might be possible to implement the idea
properly, but the CVS implementation is clearly broken.
Ian
next prev parent reply other threads:[~2004-03-25 15:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 2:06 Stan Shebs
2004-03-25 4:03 ` Ian Lance Taylor
2004-03-25 5:22 ` Jason Molenda
2004-03-25 6:19 ` Stan Shebs
2004-03-25 15:53 ` Andrew Cagney
2004-03-25 21:43 ` Ian Lance Taylor [this message]
2004-03-25 22:08 ` Jason Molenda
2004-03-25 22:37 ` Andrew Cagney
2004-03-25 22:52 ` Stan Shebs
2004-03-26 7:50 ` Andrew Cagney
2004-03-26 10:04 ` Stan Shebs
2004-03-26 14:43 ` Andrew Cagney
2004-04-02 16:25 ` Andrew Cagney
2004-04-02 16:40 ` Daniel Jacobowitz
2004-04-02 19:12 ` Stan Shebs
2004-03-25 7:35 ` Eli Zaretskii
2004-03-25 22:25 ` Stan Shebs
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=m3brmkc433.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=binutils@sources.redhat.com \
--cc=cagney@gnu.org \
--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