From: storm@cua.dk (Kim F. Storm)
Cc: monnier@iro.umontreal.ca
Subject: Re: [CVS] regex.[ch] missing in CVS checkout
Date: 05 Jan 2004 12:44:48 +0100 [thread overview]
Message-ID: <m3znd2fwlr.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <87smivtpg1.fsf@floss.red-bean.com>
Karl Fogel <kfogel@floss.red-bean.com> writes:
> Miles Bader <miles@gnu.org> writes:
> > Stefan Monnier <monnier@iro.umontreal.ca> writes:
> > > What should be done is to copy $CVSROOT/gnulib/regex.[ch],v (and not
> > > $CVSROOT/gnulib/lib/regex.[ch],v) to $CVSROOT/emacs/src.
> > > Maybe moving them would work just as well, but copying is safer.
Note that Stefan actually says "moving" is ok.
That indicates to me that emacs is really the only package
using that specific version of regex.* -- which is also the
idea you get if you look at the revision log for the files.
So is the really any reason to keep those file in sync
between gnulib and emacs repositories -- or could we
just continue to maintain the files under the emacs
repository (where they were copied some time ago) ?
> >
> > This got done a while ago... (just got back from vacation?)
> >
> > There was some talk about also adding a CVS hook to prevent
> > modifications, but I don't know if anything got done.
>
> In case this wasn't done, but someone with the requisite access wants
> to do it, a method was posted here:
>
I still don't see why this is necessary if emacs is the only
package using those files ... it must be possible to find out
if there are other packages using it (were there other symlinks
to them which have been broken?)
Maybe the original files could be made "read-only" using Karl's
code, in case we want to keep (an obsolete copy) of them in
gnulib. IMO, it would probably be better just to cvs remove
them from the gnulib repository (provided emacs was the only
package using them).
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2004-01-05 11:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031223225322.8E9BA612AA@sandy.gi.alaska.edu>
2003-12-25 1:03 ` [CVS] regex.[ch] missing in CVS checkout Miles Bader
2003-12-25 15:53 ` Kai Grossjohann
2003-12-25 16:03 ` Luc Teirlinck
2003-12-25 16:55 ` Kai Grossjohann
2003-12-26 0:25 ` Miles Bader
2003-12-27 17:17 ` Andreas Schwab
2004-01-04 22:45 ` Stefan Monnier
2004-01-04 23:32 ` Miles Bader
2004-01-04 20:43 ` Karl Fogel
2004-01-05 11:44 ` Kim F. Storm [this message]
2004-01-05 21:22 ` Karl Fogel
2004-01-06 10:01 ` Kim F. Storm
2004-01-06 21:41 ` Karl Fogel
2004-01-06 14:07 ` Richard Stallman
2004-01-05 17:56 ` Richard Stallman
2003-12-25 5:06 ` Miles Bader
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3znd2fwlr.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).