unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Rudy Gevaert <rudy@gnu.org>
Cc: Rudy Gevaert <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: Thu, 25 Dec 2003 13:21:16 -0500	[thread overview]
Message-ID: <20031225182116.GB10051@fencepost> (raw)
In-Reply-To: <jkllp0apk0.fsf@glug.org>

On Thu, Dec 25, 2003 at 10:24:15AM -0500, Thien-Thi Nguyen wrote:
> Rudy Gevaert <rudy@gnu.org> writes:
> 
>    Just to inform you about my descision.
>    Please to the necesary to fix this issue. 
> 
> what is the name of the cvs module containing the files in question?
> can people do a "cvs checkout" on this module in the usual way?
> 
> if it is not a "proper cvs module" (with an entry in some
> CVSROOT/modules file), what is the name of the containing project?
> 
> i think we can update the instructions for building emacs from cvs if we
> know these small pieces of information.

Ok.


regex.c,v -> /cvsroot/gnulib/gnulib/regex.c,v
regex.h,v -> /cvsroot/gnulib/gnulib/regex.h,v

The files can be found in the project "gnulib", module "gnulib".

Note, that these files link to the files on the OLD savannah system.
Those directories don't excist anymore.

-- 
Rudy Gevaert                rudy@gnu.org		
Web page                    http://www.webworm.org
GNU/Linux for schools       http://www.nongnu.org/glms
Savannah hacker             http://savannah.gnu.org
		                        

  reply	other threads:[~2003-12-25 18:21 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 [this message]
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
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=20031225182116.GB10051@fencepost \
    --to=rudy@gnu.org \
    --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 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).