From: "Paul W. Rankin" <pwr@sdf.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Selectively track ELPA package issues submitted to bug-gnu-emacs?
Date: Wed, 21 Aug 2019 12:05:47 +1000 [thread overview]
Message-ID: <m2v9urtgqs.fsf@sdf.org> (raw)
In-Reply-To: <CAM-tV-_JbsdmuMikY7nLhHeGp4x4md2ngVPQMBfUjm7SezSVNQ@mail.gmail.com>
Can some effort be put towards changing this for those who have donated
their work to FSF? Transitioning packages from MELPA to GNU ELPA is
currently an imbalanced value proposition. Moreover, improving the
situation would be a tide that lifts all boats.
I see that Savannah already has "items" and apparently a way to assign
these, so that could be a good option.
I'd previously been subscribed with email filters as suggested, but this
isn't an (easy) option with the current email.
p.s. I know people on this list love starting debates; this is not an
invitation for a debate, only an account of my experience. Thanks.
On Tue, Aug 20 2019, Noam Postavsky wrote:
> On Mon, 19 Aug 2019 at 01:45, Paul W. Rankin <pwr@sdf.org> wrote:
>
>> It doesn't appear that a magical connection exists between Emacs'
>> debbugs and Savannah, so what is the best way to track bugs submitted
>> to
>> bug-gnu-emacs against specific ELPA packages without needing to
>> receive
>> the entire list?
>>
>> Or does this happen automatically given I am listed as the
>> author/maintainer of said packages?
>
> No, I don't think there is a good way to do that right now, short of
> subscribing to the list and setting up email filters yourself.
next prev parent reply other threads:[~2019-08-21 2:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 3:35 Are Emacs bugs linked to Savannah? pwr
2019-08-19 5:44 ` Selectively track ELPA package issues submitted to bug-gnu-emacs? Paul W. Rankin
2019-08-20 12:32 ` Noam Postavsky
2019-08-21 2:05 ` Paul W. Rankin [this message]
2019-08-21 15:47 ` Stephen Leake
2019-08-21 23:29 ` Noam Postavsky
2019-08-22 1:42 ` Glenn Morris
2019-08-27 16:35 ` Stephen Leake
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=m2v9urtgqs.fsf@sdf.org \
--to=pwr@sdf.org \
--cc=emacs-devel@gnu.org \
--cc=npostavs@gmail.com \
/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).