all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: angeli@caeruleus.net, auctex-devel@gnu.org, emacs-devel@gnu.org,
	monnier@iro.umontreal.ca, carsten.dominik@gmail.com
Subject: Re: CVS repository synchronization for RefTeX
Date: Wed, 03 Jan 2007 09:48:07 +0100	[thread overview]
Message-ID: <8664boo5rs.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <E1H1r7W-0001v3-F0@fencepost.gnu.org> (Richard Stallman's message of "Tue\, 02 Jan 2007 16\:24\:30 -0500")

Richard Stallman <rms@gnu.org> writes:

>     I mean, let us just ask: are there any Emacs developers
>     listening who can imagine themselves working on RefTeX?
>
> I am not sure why that question is relevant.  We may have a shortage
> of people who would want to maintain RefTeX, but that isn't a matter
> of where the repository is.
>
> Given that RefTeX has a separate repository already, I don't think
> there is any harm in moving it, as such.  (I already said so.)

It hasn't: Carsten has worked on it basically without version control
or at least version logs at home.  He considered the history in the
Emacs ChangeLog to be much more relevant than what he got himself.

> However, moving it into the AUCTeX repository creates a possible
> specific risk.  Namely, the risk that AUCTeX contributors who have not
> signed papers might put changes into RefTeX also.

No, that risk does not exist.  We don't give CVS access to AUCTeX
developers not having signed papers.  The assignment problems of
AUCTeX only concern old code, and not all of it (for example,
preview-latex, a subsystem of AUCTeX, is completely covered).

>     the time frame for folding AUCTeX into Emacs will probably be
>     still years because of copyright paper reasons (we are
>     progressing there, but not really fast).
>
> Are there any current contributors to AUCTeX who have not yet signed
> papers for Emacs (which would include RefTeX)?

No.  It is only old contributors, and we covered all of the principal
ones.  The rest may be a lot of work, but the actual amounts of code
concerned are not too extensive as far as I can see.

-- 
David Kastrup

  reply	other threads:[~2007-01-03  8:48 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8664boo5rs.fsf@lola.quinscape.zz \
    --to=dak@gnu.org \
    --cc=angeli@caeruleus.net \
    --cc=auctex-devel@gnu.org \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.