unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: ddavis@ddavis.io, larsi@gnus.org, 46610@debbugs.gnu.org,
	monnier@iro.umontreal.ca
Subject: bug#46610: Interactive mode tagging for python.el navigation functions
Date: Thu, 18 Feb 2021 22:00:55 +0200	[thread overview]
Message-ID: <83pn0x403s.fsf@gnu.org> (raw)
In-Reply-To: <a9bcbf4f-7bd0-c294-a5e8-cf4e36c18adf@yandex.ru> (message from Dmitry Gutov on Thu, 18 Feb 2021 21:57:56 +0200)

> Cc: ddavis@ddavis.io, larsi@gnus.org, 46610@debbugs.gnu.org,
>  monnier@iro.umontreal.ca
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Thu, 18 Feb 2021 21:57:56 +0200
> 
> Then this part of my first reply should be most pertinent:
> 
>      Then we (someone? who?) either have to maintain both versions
> 
> Emphasis on "who".

The maintainer of python.el, I presume.

And in general, if a package is both in emacs.git and in elpa.git,
there definitely should be "someone" who takes care of it.





  reply	other threads:[~2021-02-18 20:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18  4:46 bug#46610: Interactive mode tagging for python.el navigation functions Doug Davis
2021-02-18 11:40 ` Lars Ingebrigtsen
2021-02-18 11:49   ` Dmitry Gutov
2021-02-18 11:52     ` Lars Ingebrigtsen
2021-02-18 14:41     ` Eli Zaretskii
2021-02-18 14:54       ` Dmitry Gutov
2021-02-18 15:07         ` Eli Zaretskii
2021-02-18 15:37           ` Dmitry Gutov
2021-02-18 17:25             ` Eli Zaretskii
2021-02-18 17:54               ` Dmitry Gutov
2021-02-18 19:47                 ` Eli Zaretskii
2021-02-18 19:57                   ` Dmitry Gutov
2021-02-18 20:00                     ` Eli Zaretskii [this message]
2021-02-18 20:05                       ` Dmitry Gutov
2021-02-18 15:50     ` Doug Davis

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=83pn0x403s.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=46610@debbugs.gnu.org \
    --cc=ddavis@ddavis.io \
    --cc=dgutov@yandex.ru \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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).