From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Bug trackers
Date: Tue, 26 Feb 2008 18:07:21 -0500 [thread overview]
Message-ID: <jwv8x178gr3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20080226212354.GB7406@rzlab.ucr.edu> (Don Armstrong's message of "Tue, 26 Feb 2008 13:23:54 -0800")
> Ok; creating more packages is easy, but I'll have to modify some stuff
> to create a default maintainer address for missing packages. I'll try
> to get to that later today.
Thanks.
>> I'm glad I can use non-existent packages like that. This will allow
>> us to try-and-use packages before knowing who should be the
>> corresponding maintainer (or maybe even without ever intending to
>> assign a maintainer address to it).
>>
>> I see that `index-packages' does list those non-existent packages,
>> so other than not having any maintainer is there some downside to
>> them?
> That and the "gee, I don't know about that package, you shouldn't
> assign bugs to them" message.
Indeed, in our context, debbugs shouldn't discourage reporting bugs to
packages just on the ground that they don't have a maintainer (of
course, that's only true if/when we get the above mentioned "default
maintainer address").
>> Yes. You can subscribe to them via
>> http://savannah.gnu.org/mail/?group=emacs
> Ok; Stephen indicated that installing such a handler directly in
> mailman was superior, so I'll hold off unless the gnu.org mailman
> administrators think differently or won't have time to do this
> reasonably soon.
I guess we can wait a few more days, indeed. But the sooner the merrier.
Stefan
next prev parent reply other threads:[~2008-02-26 23:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0802170200.m1H208hu013886@localhost.localdomain>
2008-02-18 5:25 ` Bug trackers Don Armstrong
2008-02-18 17:30 ` Richard Stallman
2008-02-18 23:28 ` Don Armstrong
2008-02-19 23:09 ` Richard Stallman
2008-02-19 23:18 ` Jason Rumney
2008-02-19 23:40 ` Karl Fogel
2008-02-21 2:00 ` Xavier Maillard
2008-02-21 22:28 ` Richard Stallman
2008-02-23 2:00 ` Xavier Maillard
2008-02-19 23:27 ` Don Armstrong
2008-02-20 16:44 ` Richard Stallman
2008-02-21 1:49 ` Don Armstrong
2008-02-21 21:24 ` Don Armstrong
2008-02-26 19:12 ` Stefan Monnier
2008-02-26 19:34 ` Don Armstrong
2008-02-26 20:00 ` Stefan Monnier
2008-02-26 21:23 ` Don Armstrong
2008-02-26 23:07 ` Stefan Monnier [this message]
2008-02-26 20:02 ` Stephen J. Turnbull
2008-02-27 16:08 ` Richard Stallman
2008-02-26 21:01 ` Jason Rumney
2008-02-26 21:17 ` Don Armstrong
2008-02-26 21:25 ` Stefan Monnier
2008-02-26 21:51 ` Jason Rumney
2008-02-26 23:00 ` Stefan Monnier
2008-02-26 23:02 ` Stephen J. Turnbull
2008-02-26 23:04 ` Jason Rumney
2008-02-14 4:42 Richard Stallman
2008-02-15 2:00 ` Xavier Maillard
2008-02-16 5:53 ` Richard Stallman
2008-02-17 2:00 ` Xavier Maillard
2008-02-16 8:40 ` Tassilo Horn
2008-02-16 9:16 ` Yoni Rabkin
2008-02-16 16:20 ` Tassilo Horn
2008-02-16 16:12 ` Manoj Srivastava
2008-02-16 16:53 ` Tassilo Horn
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=jwv8x178gr3.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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 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.