From: Thien-Thi Nguyen <ttn@glug.org>
Cc: rudy@gnu.org, emacs-devel@gnu.org
Subject: Re: [rudy@gnu.org: Re: [Savannah-hackers] [teirllm@dms.auburn.edu: Re: emacs/src/regex.c]]
Date: Fri, 26 Dec 2003 02:40:27 -0500 [thread overview]
Message-ID: <E1AZmaB-0000z0-00@colo.agora-net.com> (raw)
In-Reply-To: <x5y8t0ld7y.fsf@lola.goethe.zz> (message from David Kastrup on 25 Dec 2003 23:55:13 +0100)
From: David Kastrup <dak@gnu.org>
Date: 25 Dec 2003 23:55:13 +0100
Any way to do this without this presumption? Would
cvs -d :ext:anoncvs@subversions.gnu.org:/cvsroot/gnulib \
checkout gnulib/regex.{c,h}
do the trick in the script?
i don't know if cvs expands {c,h} properly but if separated into two
distinct commands i'm sure that would work:
gnulib_cvsroot=':ext:anoncvs@subversions.gnu.org:/cvsroot/gnulib'
cvs -d $gnulib_cvsroot checkout gnulib/regex.h
cvs -d $gnulib_cvsroot checkout gnulib/regex.c
for some, disk space savings is probably not as important as bandwidth
savings: 5872 KB for all of gnulib vs 212 KB for only regex.[ch].
And presuming that it does: will an update on the whole Emacs
directory update those two files via their symlinks, from their
respective repositories? Probably not, right?
correct (hence wrapping the "cvs update" operation w/ this script).
the limitation lies w/ cvs, which operates on a directory-oriented
basis, and does not handle multiple CVSROOT in one logical operation,
at least the last time i probed its failure modes in depth (~1999).
the recent change in deployment to use chroot is even more reason to
do things client-side, ugly as it may appear initially.
thi
next prev parent reply other threads:[~2003-12-26 7:40 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 [this message]
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
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
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=E1AZmaB-0000z0-00@colo.agora-net.com \
--to=ttn@glug.org \
--cc=emacs-devel@gnu.org \
--cc=rudy@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).