From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-devel@gnu.org
Subject: Re: ELPA contributions?
Date: Wed, 14 Oct 2015 12:14:50 +0100 [thread overview]
Message-ID: <877fmpem6t.fsf@russet.org.uk> (raw)
In-Reply-To: <87h9luactg.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 13 Oct 2015 10:38:35 -0700")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>> All agreed. Some packages are always going to prefer being primarily
>> on Github. But having a better bug-tracker here would make it so that
>> fewer packages feel obligated to be on Github. For let-alist, for
>> instance, I wanted to develop the package here directly, so I created
>> a github repo with no source just for the issue tracker..
>
> Who runs debbugs? How hard would it be to add a cc based on the
> Maintainer header?
Ironicaly, debbugs doesn't appear to be using debbugs at least according
to it's list of packages:
https://debbugs.gnu.org/Packages.html
Otherwise we could submit a bug/rfe there.
Phil
next prev parent reply other threads:[~2015-10-14 11:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 8:32 ELPA contributions? David Kastrup
2015-10-09 22:42 ` Artur Malabarba
2015-10-10 6:55 ` David Kastrup
2015-10-10 7:00 ` David Kastrup
2015-10-10 22:24 ` Artur Malabarba
2015-10-10 22:26 ` Artur Malabarba
2015-10-12 12:44 ` Phillip Lord
2015-10-12 16:00 ` Eric Abrahamsen
2015-10-12 20:54 ` Phillip Lord
2015-10-12 21:54 ` Artur Malabarba
2015-10-13 9:27 ` Phillip Lord
2015-10-12 21:25 ` Artur Malabarba
2015-10-12 22:14 ` Eric Abrahamsen
2015-10-12 22:32 ` Eric Abrahamsen
2015-10-13 9:35 ` Phillip Lord
2015-10-13 11:30 ` Artur Malabarba
2015-10-13 17:38 ` Eric Abrahamsen
2015-10-14 11:14 ` Phillip Lord [this message]
2015-10-12 21:44 ` Artur Malabarba
2015-10-13 11:15 ` Phillip Lord
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=877fmpem6t.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
/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.