From: Francesco Potorti` <pot@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH, RFC] etags/ctags v22.0.92 break Linux kernel `make TAGS/tags`
Date: Wed, 03 Jan 2007 01:42:16 +0100 [thread overview]
Message-ID: <E1H1uCu-00017d-8e@tucano.isti.cnr.it> (raw)
In-Reply-To: <ud55xp1f1.fsf@gnu.org>
>> After checking the behaviour of Exuberant ctags, I decided to follow the
>> same route and allow for duplicated tags in ctags mode. I added an
>> undocumented option --no-duplicates, just for emergency, that may be
>> deleted in a future release of Etags. I also undocumented the existing
>> --no-warn option.
>>
>> If anyone wants to comment on this change, please let me know.
>
>Should this change in behavior be mentioned in etc/NEWS?
I did not because the Emacs manual does not mention the ctags
functionalities of etags at all. But maybe yes, since it is only a
couple of lines in an already huge file, it probably makes sense.
prev parent reply other threads:[~2007-01-03 0:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-24 20:01 [PATCH, RFC] etags/ctags v22.0.92 break Linux kernel `make TAGS/tags` Don Mullis
2006-12-25 5:41 ` Masatake YAMATO
2006-12-25 16:47 ` Don Mullis
2006-12-25 22:36 ` Francesco Potorti`
2006-12-26 14:13 ` Francesco Potorti`
2006-12-26 18:43 ` Don Mullis
2006-12-28 0:10 ` Francesco Potorti`
2006-12-28 5:48 ` Don Mullis
2006-12-28 10:21 ` Francesco Potorti`
2006-12-29 22:58 ` Richard Stallman
2006-12-30 20:36 ` Don Mullis
2006-12-31 1:46 ` Richard Stallman
2006-12-27 2:59 ` Richard Stallman
2006-12-30 12:15 ` Francesco Potorti`
2006-12-31 1:45 ` Richard Stallman
2007-01-02 11:41 ` Francesco Potorti`
2007-01-02 14:26 ` Frank Schmitt
2007-01-03 1:24 ` Francesco Potorti`
2007-01-03 12:06 ` Frank Schmitt
2007-01-03 14:33 ` Frank Schmitt
[not found] ` <m38xgk47lc.fsf@mid.gehheimdienst.de>
2007-02-05 8:25 ` Francesco Potorti`
2007-01-02 21:24 ` Richard Stallman
2007-01-03 0:40 ` Francesco Potorti`
2007-01-02 21:24 ` Eli Zaretskii
2007-01-03 0:42 ` Francesco Potorti` [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1H1uCu-00017d-8e@tucano.isti.cnr.it \
--to=pot@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).