unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ralf Angeli <angeli@caeruleus.net>
Cc: auctex-devel@gnu.org, emacs-devel@gnu.org,
	Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: CVS repository synchronization for RefTeX
Date: Sat, 30 Dec 2006 00:43:04 +0100	[thread overview]
Message-ID: <87sley46bb.fsf@neutrino.caeruleus.net> (raw)
In-Reply-To: <jwv64buxsua.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri\, 29 Dec 2006 17\:04\:08 -0500")

* Stefan Monnier (2006-12-29) writes:

>> maintenance of RefTeX will likely be continued by the AUCTeX project.
>> On the AUCTeX developers list it is currently being discussed how
>> maintenance of RefTeX will be done in its own CVS repository.
>
> How 'bout using the Emacs-CVS as *the* repository of RefTeX?

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 would mostly
be superfluous in an Emacs release and would have to be excluded from
pretest and release tarballs, unless they are considered only a minor
annoyance.

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.

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 ...

What about branching?  IIUC CVS branches can only be created for a
whole module.  Would it be okay to create a branch for all of Emacs if
one for RefTeX only were necessary?

Another issue might be that it will be harder for people to grab the
RefTeX sources from CVS if there is a fix they are interested in.  At
least with the current structure where the documentation is in a
different directory they'd have to check out the reftex directory (to
be created) and the documentation separately.

If RefTeX is to be maintained in Emacs' repository I'd actually like
to have all files (including documentation) in one dedicated
directory.

-- 
Ralf

  reply	other threads:[~2006-12-29 23:43 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 [this message]
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
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

  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=87sley46bb.fsf@neutrino.caeruleus.net \
    --to=angeli@caeruleus.net \
    --cc=auctex-devel@gnu.org \
    --cc=carsten.dominik@gmail.com \
    --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).