unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: debbugs-gnu-bugs doesn't honor debbugs-gnu-default-packages
Date: Sat, 11 Mar 2017 21:11:20 +0100	[thread overview]
Message-ID: <87r323d15j.fsf@detlef> (raw)
In-Reply-To: <alpine.DEB.2.20.1703111744520.27617@calancha-pc> (Tino Calancha's message of "Sat, 11 Mar 2017 17:46:09 +0900 (JST)")

Tino Calancha <tino.calancha@gmail.com> writes:

> [Forwarded because i used the wrong e-mail address included in
> debbugs-gnu package.  Maybe good occasion to update it :) ]

Thanks for the hint; I've updated.

> Hi Michael,

Hi Tino,

> Command `debbugs-gnu-bugs' doesn't honor `debbugs-gnu-default-packages'.
> The addition of new packages in the bug tracker makes this command less
> convenient.  Sure, some people might want to see all bugs; but package
> maintainers probably prefer that this command just list the newest bugs
> against the package they are maintaining.

This is a deficiency only if you apply it for a range of bugs, say "the
last 10 bugs" or "all bugs between 23000 and 24000". Otherwise, it
behaves as expected.

`debbugs-gnu-bugs' is an Elisp function implementing the SOAP interface
function newest_bugs, see <http://wiki.debian.org/DebbugsSoapInterface>.
No other filters are applied.

> If it's hard to make `debbugs-gnu-bugs' follow `debbugs-gnu-default-packages'
> maybe we should add a new command to provide such functionality i.e.,
> to list the newest bugs filled against a package in
> `debbugs-gnu-default-packages'.
>
> I don't know how to implement this.  Any advice would be much
> appreciated.

We could extend `debbugs-gnu' for this. The back side is, that we could
decide client side only. That means, we retrieve all bugs which match
`debbugs-gnu-default-packages', but show then only the bugs "between
23000 and 24000". This is suboptimal in terms of performance.

Let me think about.

> Regards,
> Tino



       reply	other threads:[~2017-03-11 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.20.1703111744520.27617@calancha-pc>
2017-03-11 20:11 ` Michael Albinus [this message]
2017-03-11  8:43 debbugs-gnu-bugs doesn't honor debbugs-gnu-default-packages Tino Calancha

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=87r323d15j.fsf@detlef \
    --to=michael.albinus@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=tino.calancha@gmail.com \
    /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).