From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: auctex-devel@gnu.org, emacs-devel@gnu.org
Subject: Re: CVS repository synchronization for RefTeX
Date: Sat, 30 Dec 2006 17:07:04 -0500 [thread overview]
Message-ID: <jwvvejtujzx.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87sley46bb.fsf@neutrino.caeruleus.net> (Ralf Angeli's message of "Sat\, 30 Dec 2006 00\:43\:04 +0100")
> There will be standalone releases of RefTeX. That means files for
> building and installing RefTeX as well as files like README, INSTALL,
> etc. would have to be added to Emacs' repository.
Those can easily be put into the `admin' subdirectory which is not included
in Emacs releases.
> And we'll probably have to jump through some hoops for building
> documentation and putting it into a RefTeX tarball as reftex.texi
> currently is located in the man directory.
Right, you'd have to do a bit of extra work to bring the various files from
`admin', `man', `lisp', ... into a single directory when building
the tarball.
> Then there might be the problem that RefTeX is not in a releasable
> state at the time an Emacs release is about to happen. Suppose I
> would have had a major and risky change for RefTeX waiting to be
> checked in about a year ago and held it back because Emacs is about to
> be released. I'd probably still not have it checked in. Such a
> situation nothing I'd be looking forward to. Of course in an urgent
> case one can back out such changes, but if you can avoid it ...
That's what branches are for. No problem here.
> What about branching? IIUC CVS branches can only be created for a
> whole module.
You understand incorrectly. In CVS each file is handled separately (so to
a large extent, the notion of "module" only exists in the documentation of
CVS rather than in its code and behavior), so you can have separate branches
on a file-by-file basis. It's generally saner to have the same branches on
"every" file, but it's perfectly OK to have a branch only on a well-defined
subset of the files, such as have a RefTeX-only branch on the
RefTeX-related files.
> Would it be okay to create a branch for all of Emacs if
> one for RefTeX only were necessary?
That would be OK as well, although not needed.
> If RefTeX is to be maintained in Emacs' repository I'd actually like
> to have all files (including documentation) in one dedicated
> directory.
That would probably not be an option. Although, starting from the Arch
version of Emacs's repository, you could easily create an Arch archive for
RefTeX which automatically tracks all the RefTeX files (and only them), and
placed in a single directory or any other way you want.
Stefan
next prev parent reply other threads:[~2006-12-30 22:07 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 22:53 CVS repository synchronization for RefTeX Ralf Angeli
2006-12-29 22:04 ` Stefan Monnier
2006-12-29 23:43 ` Ralf Angeli
2006-12-30 14:20 ` Eli Zaretskii
2006-12-30 15:08 ` Ralf Angeli
2006-12-30 15:20 ` Eli Zaretskii
2006-12-30 16:01 ` Ralf Angeli
2006-12-30 16:47 ` Carsten Dominik
2006-12-30 18:03 ` Eli Zaretskii
2006-12-30 18:50 ` Ralf Angeli
2006-12-30 19:03 ` Eli Zaretskii
2006-12-30 19:18 ` Ralf Angeli
2006-12-31 1:46 ` Richard Stallman
2006-12-30 21:28 ` Alan Shutko
2006-12-30 21:55 ` Reiner Steib
2006-12-31 22:27 ` Giorgos Keramidas
2006-12-31 23:57 ` Ralf Angeli
2007-01-01 7:09 ` Ways of keeping Emacs 22 and external projects in sync (was: CVS repository synchronization for RefTeX) Michael Olson
2007-01-01 15:21 ` Ways of keeping Emacs 22 and external projects in sync Ralf Angeli
2007-01-01 17:59 ` Reiner Steib
2007-01-01 18:36 ` Giorgos Keramidas
2007-01-03 10:43 ` Yavor Doganov
2007-01-03 18:32 ` Michael Olson
2007-01-03 18:29 ` Michael Olson
2007-01-03 19:53 ` Ralf Angeli
2007-01-03 22:37 ` Michael Olson
2007-01-01 18:20 ` Ways of keeping Emacs 22 and external projects in sync (was: CVS repository synchronization for RefTeX) Giorgos Keramidas
2007-01-01 21:56 ` CVS repository synchronization for RefTeX Richard Stallman
2006-12-30 18:23 ` Richard Stallman
2006-12-30 18:39 ` Ralf Angeli
2006-12-31 1:47 ` Richard Stallman
2007-01-01 16:01 ` David Kastrup
2007-01-02 3:09 ` Richard Stallman
2007-01-02 7:43 ` David Kastrup
2007-01-02 21:24 ` Richard Stallman
2007-01-03 8:48 ` David Kastrup
2007-01-04 2:31 ` Richard Stallman
2007-01-04 21:51 ` David Kastrup
2007-01-06 2:54 ` Richard Stallman
2007-01-06 9:14 ` David Kastrup
2006-12-30 21:54 ` Reiner Steib
2006-12-31 19:36 ` Ralf Angeli
2007-01-01 17:59 ` Reiner Steib
2007-01-01 19:12 ` Ralf Angeli
2006-12-30 22:07 ` Stefan Monnier [this message]
2006-12-29 22:59 ` Richard Stallman
2006-12-30 17:00 ` David Kastrup
2007-01-07 21:42 ` Bill Wohler
2007-01-08 19:25 ` [AUCTeX-devel] " Ralf Angeli
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=jwvvejtujzx.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=auctex-devel@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 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.