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 12:15:53 +0100	[thread overview]
Message-ID: <f7ccd24b0902010315s1b4eddb6h843c2fb7d1ba57ba@mail.gmail.com> (raw)
In-Reply-To: <20090201040218.GZ4175@volo.donarmstrong.com>

On Sun, Feb 1, 2009 at 05:02, Don Armstrong <don@donarmstrong.com> wrote:

> I'd rather not waste time trying to work around problems and
> misconceptions brought about by the use of invented non-standard
> nomenclature to describe how debbugs operates. [In actual fact, I
> probably won't spend the time dealing with such issues at all.]

It is clear that what I'm describing as a "label" is just what you
call a "package that has not been created". The fact they are
initially arbitrary labels is highlighted by the fact that

  reassign N this-nonexistent-package

works (with a warning), and then you can search for
this-nonexistent-package. If packages were so first-order objects, it
would be impossible to assign one to a nonexistent one.

> No. You can search for bugs which have package "rmail".

Yes. That's exactly what I was saying. But, until you create the
package rmail, "rmail" is only a label (even if you and debbugs don't
call it so).

> There is no
> such thing as a label in debbugs. The package a bug is assigned to has
> nothing to do with whether the package is known to exist. Debbugs only
> cares about what is in the package field of the bug when searching for
> bugs.

Which agrees 100% with what I said, except by nomenclature.

    Juanma




  reply	other threads:[~2009-02-01 11:15 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
2009-02-01  4:02             ` Don Armstrong
2009-02-01 11:15               ` Juanma Barranquero [this message]
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=f7ccd24b0902010315s1b4eddb6h843c2fb7d1ba57ba@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).