all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: debbugs Emacs package names
Date: Fri, 15 Jul 2011 12:39:10 -0400	[thread overview]
Message-ID: <vv7h7jcxch.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m3bowv7hkf.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Fri, 15 Jul 2011 16:18:56 +0200")

Lars Magne Ingebrigtsen wrote:

> I wonder whether there's much point in tagging stuff as "emacs,gnus" or
> "emacs,org-mode".  Presumably the Gnus and Org maintainers will deal
> with these bugs, so would it make sense to just assign them solely to
> "gnus" and "org-mode"?

It's not tagging, it's reassigning, and it affects where bug mails go.

I think that if someone reports a bug to bug-gnu-emacs, they expect to
see subsequent mails about it appear on that list, so things should
generally stay in the "emacs" package. Since both Org and Gnus have
separate bug reporting addresses, people who want to can use those
channels instead from the start.

When something has been reported as an "emacs" bug, I'm not sure
assigning it to eg "emacs,gnus" really adds much value, but I figure it
doesn't do any harm.

> And should we do the same for other external/internal-packages like
> cperl-mode? 

I advise against it. I did more of putting things in packages at the
start, and it turned out not to be worth it. It doesn't add much value
(eg a subject search is often just as good a way to find relevant bugs),
and it makes merging harder. I only do it now when there is a real
alternative bug maling list (eg gnus, cc-mode). Even then I'm not sure
it adds much. Do you as a Gnus developer find it helps you in any way?



  reply	other threads:[~2011-07-15 16:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15 14:18 debbugs Emacs package names Lars Magne Ingebrigtsen
2011-07-15 16:39 ` Glenn Morris [this message]
2011-07-15 17:09   ` Lars Magne Ingebrigtsen
2011-07-17 14:11 ` Stefan Monnier

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=vv7h7jcxch.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --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.