From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>,
Tino Calancha <tino.calancha@gmail.com>,
wsnyder@wsnyder.org
Subject: Re: Comment in verilog-mode.el about supported versions
Date: Mon, 19 Dec 2016 08:09:13 -0500 [thread overview]
Message-ID: <CAM-tV-96aPLQoQiQj3E=YYg237JMDiP2B2H0KueO18cBZ=bpfw@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY3SPHGTYkQvGnhoksCXvzsmWnt7DQEdv+sZYuZKof3Xgg@mail.gmail.com>
On Mon, Dec 19, 2016 at 8:02 AM, Kaushal Modi <kaushal.modi@gmail.com> wrote:
> Copying Wilson Snyder.
>
> On Mon, Dec 19, 2016, 5:19 PM Tino Calancha <tino.calancha@gmail.com> wrote:
>>
>>
>> Hi,
>>
>> in the comentary of
>> lisp/progmodes/verilog-mode.el
>> you can find following comment:
>> ;; This code supports Emacs 21.1 and later
>> ;; And XEmacs 21.1 and later
>> ;; Please do not make changes that break Emacs 21. Thanks!
>>
>> I could understand this comment in a version of this file
>> elsewhere, e.g. ELPA, but not in the built-in version in Emacs.
>> Why is this comment needed?
>> Is it OK to drop from the master branch this kind of comments?
This reminds me, I posted a patch to fix a bug in verilog-mode, but
left it unapplied because I wasn't sure about backwards compatibility:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23842#62
next prev parent reply other threads:[~2016-12-19 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 11:49 Comment in verilog-mode.el about supported versions Tino Calancha
2016-12-19 13:02 ` Kaushal Modi
2016-12-19 13:09 ` Noam Postavsky [this message]
2016-12-19 13:47 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2016-12-19 13:37 Wilson Snyder
2016-12-19 14:02 ` Tino Calancha
2016-12-19 15:02 ` Stefan Monnier
2016-12-19 14:32 Wilson Snyder
2016-12-19 15:35 ` Tino Calancha
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='CAM-tV-96aPLQoQiQj3E=YYg237JMDiP2B2H0KueO18cBZ=bpfw@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=tino.calancha@gmail.com \
--cc=wsnyder@wsnyder.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.