From: Chong Yidong <cyd@gnu.org>
To: Ralf Angeli <angeli@caeruleus.net>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: RefTeX Merge
Date: Wed, 26 Sep 2012 18:20:48 +0800 [thread overview]
Message-ID: <87ehlphypr.fsf@gnu.org> (raw)
In-Reply-To: <871uhri21g.fsf@caeruleus.net> (Ralf Angeli's message of "Mon, 24 Sep 2012 22:44:27 +0200")
Ralf Angeli <angeli@caeruleus.net> writes:
>> No. Since reftex.el is one file, it is not worth creating a
>> subdirectory just for it.
>
> RefTeX consists of eleven Lisp files. It might not be a bad idea to put
> them into their own directory.
Sorry, my mistake.
But I have to agree with RMS; it still doesn't seem worth giving reftex
its own subdirectory.
>> Putting them in the commit log may be a fine solution.
>
> If the log can take such amount of data, then I would be fine with it.
> And besides that I'd prepare a shorter entry for the ChangeLog file.
From my estimation, once you take out entries for Makefile changes,
releases, and synchs to Emacs, the ChangeLog is about 400 lines, which
is manageable. So I think we can put it in the commit log.
In the version to be added to the ChangeLog file, you can collate the
changes to each file, which should shorten the entry significantly.
Still, I think a ChangeLog entry of ~100 lines is acceptable.
>> (Normally, one would use bzr join to
>> preserve the history, but bzr join seems to be badly broken.)
>
> Now that would be a nice solution. RefTeX is currently maintained in
> a CVS repository, though. I'm not sure if this makes matters better
> or worse.
Let's not play with bzr join. We've had bad experiences with that on
the elpa branch.
I suggest just patching the affected files manually, then committing as
though you had made the changes in one shot. Just be sure not to
inadvertently change the headers (e.g. "This file is part of GNU Emacs")
and so forth.
next prev parent reply other threads:[~2012-09-26 10:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 18:10 RefTeX Merge Ralf Angeli
2012-09-23 18:39 ` Paul Eggert
2012-09-24 6:13 ` Chong Yidong
2012-09-24 20:44 ` Ralf Angeli
2012-09-24 23:32 ` Richard Stallman
2012-09-25 6:30 ` Tassilo Horn
2012-09-26 6:11 ` Ralf Angeli
2012-09-26 7:09 ` Tassilo Horn
2012-09-26 7:59 ` Stephen J. Turnbull
2012-09-26 13:20 ` Stefan Monnier
2012-09-26 10:20 ` Chong Yidong [this message]
2012-09-26 13:24 ` Subdirectories in `lisp' Stefan Monnier
2012-09-30 20:46 ` RefTeX Merge Ralf Angeli
2012-09-23 18:48 ` Glenn Morris
2012-09-23 18:58 ` Glenn Morris
2012-09-23 19:09 ` Glenn Morris
2012-09-24 1:42 ` Glenn Morris
2012-09-24 1:50 ` Glenn Morris
2012-09-24 21:02 ` Ralf Angeli
2012-10-16 7:39 ` Tassilo Horn
2012-11-01 14:05 ` 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=87ehlphypr.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=angeli@caeruleus.net \
--cc=eggert@cs.ucla.edu \
--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.