Re: Backporting changes into emacs-23 prior to pretest

[Chong Yidong <cyd@stupidchicken.com>]

Dan Nicolaescu <dann@gnu.org> writes:

> How about this one:
>    ** Directory local variables can apply to file-less buffers.
>    For example, adding "(diff-mode . ((mode . whitespace)))" to your
>    .dir-locals.el file, will turn on `whitespace-mode' for *vc-diff* buffers.
> The code change itself is small, and only touches one or two
> functions.

I don't think this is a good candidate for backporting, but if you feel
strongly about it, we can discuss more.

> How about the changes to make major modes derive from `prog-mode'?
> [This is not quite finished, but it won't be too hard to finish it...]

These is mostly a cleanup, right?  I don't think it's worth backporting
either.

>> (One set of changes that I think would be good to backport are the
>> improvements to VC since emacs-23 was branched.  However, this is
>> complicated by the fact that the Lisp files have been moved into a vc/
>> directory in the trunk, so I'm not sure how to go about merging them.
>> Does anyone have a suggestion?)
>
> Copy the files from trunk over to the branch.  AFAIR there's nothing
> that depends on changes to the core, so just copying should be fine.

OK, I've done this.  Thanks.