From: Ralf Angeli <angeli@caeruleus.net>
Cc: auctex-devel@gnu.org, emacs-devel@gnu.org
Subject: Re: CVS repository synchronization for RefTeX
Date: Mon, 01 Jan 2007 20:12:54 +0100 [thread overview]
Message-ID: <87wt46a7d5.fsf@neutrino.caeruleus.net> (raw)
In-Reply-To: <v9mz52fx0u.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon\, 01 Jan 2007 18\:59\:45 +0100")
* Reiner Steib (2007-01-01) writes:
> On Sun, Dec 31 2006, Ralf Angeli wrote:
>
>> What I dislike about it is that the files will be scattered throughout
>> Emacs' repository. This makes fetching the "package" RefTeX from CVS
>> much more complicated. And with the branch it would get even harder
>> if people want to fetch a development version.
>
> If I understand Stefan correctly, it's possible to create a branch
> with just the RefTeX relevant files.
I have yet to find documentation of such a feature. The only thing
I've found was a usenet post warning not to branch selected files
only, because CVS gets confused when updating or commiting in a
directory containing branched and non-branched files. Such a mix
might not happen with the setup proposed by Stefan, however.
>> Also stuff like `C-x 4 a' won't work with such a file layout and a
>> single ChangeLog file.
>
> A the changes would be done in the Emacs CVS directory layout, also
> these ChangeLog files (lisp/ChangeLog, man/ChangeLog) should be used.
> No problem with `C-x 4 a'.
And what about standalone releases? Would those be shipped with
ChangeLog files for each directory? We'd probably have to clean those
files in the branch of any entries not related to RefTeX.
> I played a bit with the following[1] sketch of admin/reftex/Makefile.
> Using grep-changelog we can build RefTeX-only ChangeLog files
Okay, that would be another approach.
I still cannot say that I am too enthusiastic about maintaining a
package when its files are scattered throughout a larger repository.
--
Ralf
next prev parent reply other threads:[~2007-01-01 19:12 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 [this message]
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=87wt46a7d5.fsf@neutrino.caeruleus.net \
--to=angeli@caeruleus.net \
--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.