all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ralf Angeli <angeli@caeruleus.net>
To: Chong Yidong <cyd@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: RefTeX Merge
Date: Mon, 24 Sep 2012 22:44:27 +0200	[thread overview]
Message-ID: <871uhri21g.fsf@caeruleus.net> (raw)
In-Reply-To: <876274lzio.fsf@gnu.org> (Chong Yidong's message of "Mon, 24 Sep 2012 14:13:03 +0800")

* Chong Yidong (2012-09-24) writes:

> Paul Eggert <eggert@cs.ucla.edu> writes:
>
>> One possibility is to create a new directory
>> lisp/textmodes/reftex, move the RefTeX source there,
>> and create a ChangeLog there, starting the ChangeLog with all the
>> old history followed by a note saying what happened.
>
> 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.

> When a file is synched to the Emacs repository, the ChangeLog typically
> only describes the differences relative to the previous version.  That's
> usually a truncated version of the file's full ChangeLog history, but in
> practice this hasn't been a big problem.  Adding a big mass of ChangeLog
> entries is not very helpful for people browsing the Emacs ChangeLog.

That's where a separate ChangeLog file could make sense.  But I agree
that it would not be a good idea to put the whole ChangeLog from the
standalone version in there.  I'd have to check how much effort it would
be to write down the changes relative to the current version in Emacs.
It could be a bit of work. (c:

> How large are the ChangeLog entries in question?

The ChangeLog is about 26 kB.  One could shave off a bit of it by
removing the entries related to the Makefiles.  Here is a link if you
want to have a look:

http://cvs.savannah.gnu.org/viewvc/reftex/ChangeLog?root=auctex&view=markup

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

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

-- 
Ralf



  reply	other threads:[~2012-09-24 20:44 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 [this message]
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
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=871uhri21g.fsf@caeruleus.net \
    --to=angeli@caeruleus.net \
    --cc=cyd@gnu.org \
    --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.