From: Miles Bader <miles@gnu.org>
Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
Subject: Re: [CVS] regex.[ch] missing in CVS checkout
Date: Thu, 25 Dec 2003 19:25:37 -0500 [thread overview]
Message-ID: <20031226002537.GA23431@fencepost> (raw)
In-Reply-To: <87ptecrg5s.fsf@emptyhost.emptydomain.de>
On Thu, Dec 25, 2003 at 05:55:11PM +0100, Kai Grossjohann wrote:
> > They are symlinked to gnulib/regex [ch] (not to be confused with
> > gnulib/src/regex [ch]) according to an old message by Stefan.
>
> My Emacs checkout is in ~/work/gnu/emacs. I did:
...
> $FOO is what the CVS instructions say for anon checkout of the gnulib
> project.
This is one way to do it, however it's obviously a pain for people checking
out emacs.
Another way would be to do what used to be done, and simply keep separate
copies of regex.[ch] in emacs, merging back and forth with the official
gnulib copies as necessary.
If changes to regex.[ch] occur somewhat rarely, I'd say the latter method is
better.
-Miles
--
`Cars give people wonderful freedom and increase their opportunities.
But they also destroy the environment, to an extent so drastic that
they kill all social life' (from _A Pattern Language_)
next prev parent reply other threads:[~2003-12-26 0:25 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 [this message]
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
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=20031226002537.GA23431@fencepost \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
/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).