unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: auctex-devel@gnu.org, carsten.dominik@gmail.com, emacs-devel@gnu.org
Subject: Re: CVS repository synchronization for RefTeX
Date: Sat, 30 Dec 2006 17:20:34 +0200	[thread overview]
Message-ID: <uirft2ywt.fsf@gnu.org> (raw)
In-Reply-To: <87mz554e1u.fsf@neutrino.caeruleus.net> (message from Ralf Angeli on Sat, 30 Dec 2006 16:08:13 +0100)

> From: Ralf Angeli <angeli@caeruleus.net>
> Cc: auctex-devel@gnu.org,  emacs-devel@gnu.org,  carsten.dominik@gmail.com
> Date: Sat, 30 Dec 2006 16:08:13 +0100
> 
> * Eli Zaretskii (2006-12-30) writes:
> 
> >> From: Ralf Angeli <angeli@caeruleus.net>
> >> 
> >> There will be standalone releases of RefTeX.
> >
> > Why?
> 
> Because I don't want to couple the Emacs and RefTeX release cycles.

But you might need to do that anyway, since some Emacs features used
by RefTeX will require a newer Emacs.

Besides, why not couple them?  What's the problem?

> > What problems is this going to solve that cannot be solved by
> > telling people to fetch files from the Emacs CVS?
> 
> I already answered part of that question in my last mail.

What, the need to get several files from different directories?
That's a non-issue, since a problem that urges a user to fetch a newer
file is normally solved in a single directory, if not a single file.
There's no need to fetch the docs if the problem is in Lisp.

> Apart from
> that there are many users who are not really acquainted with CVS
> (okay, there's the web interface) and with "installing" and
> byte-compiling single files.  And if those users manage to do that
> (probably by handholding them through the process) they'll get some
> hodgepodge of files from releases and CVS.  And providing support for
> such hodgepodge installations will be quite a nightmare.  I'd really,
> _really_ like to avoid such a mess.

This whole mess (and then some) will be completely avoided if you
decide to stick with Emacs releases.  If you don't, releasing interim
versions will get you at least some of the trouble, since users will
be installing those versions in several Emacs versions, and you will
have problem knowing which ones (as many people nowadays use the CVS
code).

I really, _really_ urge you to reconsider.

  reply	other threads:[~2006-12-30 15:20 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 [this message]
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=uirft2ywt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).