all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: Dove Young <dove.young@gmail.com>,
	Chong Yidong <cyd@stupidchicken.com>,
	8802@debbugs.gnu.org
Subject: bug#8802: cperl-write-tags function in cperl-mode.el hard coded tags-file-name
Date: Wed, 06 Jul 2011 15:35:42 -0400	[thread overview]
Message-ID: <eoaacrurqp.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m3sjqjxobk.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 06 Jul 2011 20:21:19 +0200")

Lars Magne Ingebrigtsen wrote:

> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> I'd rather that such a change be installed in Ilya's upstream
>> version first.  We already have plenty of merge problems because of
>> patches he rejected.

This always makes me wonder: what is the point of having a file in Emacs
where modifying it is not allowed (or at least, is strongly
discouraged)? Why not move it to GNU ELPA? It's not like there isn't
another perl mode in Emacs, which is actually used by default.
	
> Right. Would forwarding the report to Ilya and closing the bug report
> in debbugs be the right thing to do?

Debbugs has the ability to mark a report as forwarded, see
http://debbugs.gnu.org/Developer.html#forward

Such reports are not usually closed.





  reply	other threads:[~2011-07-06 19:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-05  3:36 bug#8802: cperl-write-tags function in cperl-mode.el hard coded tags-file-name Dove Young
2011-07-06 17:14 ` Lars Magne Ingebrigtsen
2011-07-06 18:15   ` Stefan Monnier
2011-07-06 18:21     ` Lars Magne Ingebrigtsen
2011-07-06 19:35       ` Glenn Morris [this message]
2011-07-06 19:51         ` Stefan Monnier
2011-07-06 19:54           ` Lars Magne Ingebrigtsen
2020-11-19  5:19     ` Stefan Kangas

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=eoaacrurqp.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=8802@debbugs.gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=dove.young@gmail.com \
    --cc=larsi@gnus.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.