all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Backporting changes into emacs-23 prior to pretest
Date: Sun, 24 Oct 2010 20:02:00 -0400	[thread overview]
Message-ID: <yxq1v7fqgw7.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87aam38rr0.fsf@stupidchicken.com> (Chong Yidong's message of "Sun\, 24 Oct 2010 12\:44\:51 -0400")

Chong Yidong <cyd@stupidchicken.com> writes:

> In preparation for the Emacs 23.3 pretest, I'd like to ask everyone if
> there are any specific parts of the trunk you'd like to see backported.
> The 23.3 release will be mostly bugfixes, so significant new features
> will not be considered.  However, updated "stable" versions of exsiting
> modes and packages should be acceptable.

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.

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

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




  reply	other threads:[~2010-10-25  0:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-24 16:44 Backporting changes into emacs-23 prior to pretest Chong Yidong
2010-10-25  0:02 ` Dan Nicolaescu [this message]
2010-11-03 18:39   ` Chong Yidong
2010-11-04  3:09     ` Dan Nicolaescu
2010-11-04 14:17       ` Stefan Monnier
2010-10-26  7:16 ` Ulrich Mueller
2010-11-03 18:56   ` Chong Yidong
2010-11-03 20:18     ` Ulrich Mueller

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=yxq1v7fqgw7.fsf@fencepost.gnu.org \
    --to=dann@gnu.org \
    --cc=cyd@stupidchicken.com \
    --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.