all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Alan Mackenzie <acm@muc.de>
Cc: David Reitter <david.reitter@gmail.com>,
	Katsumi Yamaoka <yamaoka@jpl.org>,
	emacs-devel@gnu.org
Subject: supporting older versions of emacs (was: Re: bootstrap fails AND how about fixing the byte-compiler?)
Date: Tue, 15 Jan 2008 21:47:30 -0800	[thread overview]
Message-ID: <200801160547.m0G5laV0007175@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <20080116001356.GA3081@muc.de> (Alan Mackenzie's message of "Wed,  16 Jan 2008 00:13:56 +0000")

Alan Mackenzie <acm@muc.de> writes:

  > Anyhow, it seems the best solution for cc-vars.el right now (after all,
  > it's got to work with Emacs 2[01] and various flavours of XEmacs, too),
  > is to change c-constant-symbol into a macro.  

It's obviously your choice, but is it worth it to still support
emacs-20? 
21.1 was released in October 2001. 
Is the number of people that do not upgrade to emacs-21, but still want
to use the latest cc-mode significant enough to be worth the trouble?

  parent reply	other threads:[~2008-01-16  5:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1JEXu8-0004C3-Cy@cvs.savannah.gnu.org>
2008-01-15  0:03 ` bootstrap fails Katsumi Yamaoka
2008-01-16  0:13   ` bootstrap fails AND how about fixing the byte-compiler? Alan Mackenzie
2008-01-16  0:58     ` Miles Bader
2008-01-16  2:15     ` Katsumi Yamaoka
2008-01-16  5:47     ` Dan Nicolaescu [this message]
2008-01-16  8:12       ` supporting older versions of emacs Glenn Morris
2008-01-16 21:21         ` Alan Mackenzie
2008-01-16 22:29           ` Reiner Steib
2008-01-16 22:58             ` Glenn Morris
2008-01-16 23:41               ` Reiner Steib
2008-01-16 21:31       ` supporting older versions of emacs (was: Re: bootstrap fails AND how about fixing the byte-compiler?) Alan Mackenzie
2008-01-16 23:40         ` Dan Nicolaescu

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=200801160547.m0G5laV0007175@sallyv1.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=acm@muc.de \
    --cc=david.reitter@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=yamaoka@jpl.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.