all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: Eli Zaretskii <eliz@elta.co.il>, emacs-devel@gnu.org
Subject: Re: [rudy@gnu.org: Re: [Savannah-hackers] [teirllm@dms.auburn.edu: Re:	emacs/src/regex.c]]
Date: 26 Dec 2003 01:19:51 +0100	[thread overview]
Message-ID: <m3vfo42zx4.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <20031225213656.GB17775@fencepost>

Rudy Gevaert <rudy@gnu.org> writes:

> On Thu, Dec 25, 2003 at 10:21:45PM +0200, Eli Zaretskii wrote:
> > If symlinks are not the right thing to do, what is?  Checking out
> > regex.[ch] from their CVS and checking them into the Emacs CVS?  I
> 
> Yes

Since there are _vital_ branch and release tagging information in the
old regex.[ch] files related to GNU emacs, it would be inadequate to
just commit the latest version of those files into the emacs
repository.

The only proper solution is to _copy_ the two ,v files directly (on
the CVS server) into the emacs repository, to preserve consistency &
history.

> 
> > thought the links were used to avoid the need to resync the two
> > repositories manually; is there a better way to do that?
> 
> That could be.  I don't know who set up those symlinks.  In our
> previous configuration it was possible.  Now, every project runs in a
> chroot.  Linking outside this chroot doesn't seem to be the right
> thing to do.
> 
> I even doubt if it is possible.  If it is, I could be that this breaks
> (or could be exploited) the chroot environment.

I don't think it is worth it.  The symlinks were a hack whose time has
gone...

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2003-12-26  0:19 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-25 14:50 [rudy@gnu.org: Re: [Savannah-hackers] [teirllm@dms.auburn.edu: Re: emacs/src/regex.c]] Rudy Gevaert
2003-12-25 15:24 ` Thien-Thi Nguyen
2003-12-25 18:21   ` Rudy Gevaert
2003-12-25 21:21     ` Thien-Thi Nguyen
2003-12-25 22:55       ` David Kastrup
2003-12-26  7:40         ` Thien-Thi Nguyen
2003-12-26 10:01           ` Eli Zaretskii
2003-12-26 10:16             ` Thien-Thi Nguyen
2003-12-26  7:43         ` Thien-Thi Nguyen
2003-12-26 13:33           ` David Kastrup
2003-12-26 15:34     ` Richard Stallman
2003-12-25 20:21 ` Eli Zaretskii
2003-12-25 21:36   ` Rudy Gevaert
2003-12-26  0:19     ` Kim F. Storm [this message]
2003-12-26  8:27       ` Rudy Gevaert
2003-12-26 16:40       ` Kai Grossjohann
2003-12-27 21:39         ` Kim F. Storm
2003-12-27  4:13       ` Richard Stallman
2003-12-27  8:17         ` Rudy Gevaert
2003-12-27 11:19           ` Jason Rumney
2003-12-27 21:58           ` Kim F. Storm
2003-12-27 21:05             ` Rudy Gevaert
2003-12-27 22:06             ` Sam Steingold
2003-12-28  6:10               ` Eli Zaretskii
2003-12-28  6:28                 ` Miles Bader
2003-12-29 11:54                   ` Richard Stallman
2003-12-28  8:35                 ` Kenichi Handa
2003-12-28 20:49               ` Richard Stallman
2003-12-28 20:50           ` Richard Stallman
2003-12-28 23:51             ` Karl Fogel
2003-12-30  1:25               ` Richard Stallman

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=m3vfo42zx4.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=eliz@elta.co.il \
    --cc=emacs-devel@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.