unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Don't report new bugs for Rmail??
Date: Sun, 1 Feb 2009 02:00:37 +0100	[thread overview]
Message-ID: <f7ccd24b0901311700x6d15fc04ya339ad8ed1768b1e@mail.gmail.com> (raw)
In-Reply-To: <20090131211929.GT4175@volo.donarmstrong.com>

On Sat, Jan 31, 2009 at 22:19, Don Armstrong <don@donarmstrong.com> wrote:

> They're not "just arbitrary labels".

Packages are not arbitrary labels. "Packages" are. I said that
packages are "packages" (i.e., labels) plus other things.

What I was saying, in other words, is that you can assign a bug to any
arbitrary label, but that the label is not a real package unless the
package exists.

> Bug reports against packages that don't have a maintainer shouldn't be
> submitted, because there's no indication that someone is going to look
> at them. In this case, the error is that no one has asked for the
> rmail package to be created.

But still, you can search for the label "rmail" even if no package exists.

    Juanma




  parent reply	other threads:[~2009-02-01  1:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-31 10:21 Don't report new bugs for Rmail?? Eli Zaretskii
2009-01-31 10:44 ` Don Armstrong
2009-01-31 11:19   ` Eli Zaretskii
2009-01-31 11:28     ` Juanma Barranquero
2009-01-31 12:47       ` Eli Zaretskii
2009-01-31 21:19         ` Don Armstrong
2009-01-31 21:54           ` Eli Zaretskii
2009-01-31 22:24             ` Don Armstrong
2009-02-01  4:14               ` Eli Zaretskii
2009-02-01  4:33                 ` Don Armstrong
     [not found]                   ` <utz7ec9r6.fsf@gnu.org>
2009-02-01 21:14                     ` Don Armstrong
2009-02-02  1:47                     ` Glenn Morris
2009-02-02  2:20                       ` Glenn Morris
2009-02-02  2:22                         ` Glenn Morris
2009-02-02  3:23                           ` Glenn Morris
2009-02-02 18:48                         ` Glenn Morris
2009-02-02 19:18                           ` Don Armstrong
2009-02-02 20:30                             ` Eli Zaretskii
2009-02-02 21:16                             ` Stefan Monnier
2009-02-02 20:26                           ` Eli Zaretskii
2009-02-02 21:17                           ` Stefan Monnier
2009-02-01  6:22               ` Jason Rumney
2009-02-01 11:17                 ` Juanma Barranquero
2009-02-01 20:34                 ` Don Armstrong
2009-02-01 21:15               ` Stefan Monnier
2009-02-01  1:00           ` Juanma Barranquero [this message]
2009-02-01  4:02             ` Don Armstrong
2009-02-01 11:15               ` Juanma Barranquero
2009-02-01 11:18                 ` Juanma Barranquero
     [not found]           ` <E1LTl7o-0005Ea-FN@fencepost.gnu.org>
2009-02-02  7:36             ` Don Armstrong
2009-02-03  1:43               ` Richard M Stallman
2009-01-31 19:51 ` 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

  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=f7ccd24b0901311700x6d15fc04ya339ad8ed1768b1e@mail.gmail.com \
    --to=lekktu@gmail.com \
    --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 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).