From: Michael Albinus <michael.albinus@gmx.de>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: larsi@gnus.org, Emacs developers <emacs-devel@gnu.org>
Subject: Re: debbugs-0.10: two comments
Date: Tue, 13 Sep 2016 14:06:02 +0200 [thread overview]
Message-ID: <8760q0dmxh.fsf@gmx.de> (raw)
In-Reply-To: <8737l5sin0.fsf@gmx.de> (Michael Albinus's message of "Mon, 12 Sep 2016 09:05:07 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
Hi Tino,
> I agree, debbugs-gnu-trunk-directory and debbugs-gnu-branch-directory
> should be user options. Will change.
>
> In debbugs-gnu-apply-patch, it will be checked already whether this is
> set properly. If not, the directory name is requested
> interactively. Shall be done in other functions as well; I'll change
> this.
Done.
> I have already plans to extend debbugs-gnu-bugs and debbugs-org-bugs.
> Currently, they allow only list of bug numbers, like "100,200,300" etc.
> I want to allow also ranges, like "100-200,300-400" and so on. A special
> range "-10" could mean then "the last 10 bugs". This shall fit your needs.
Done also. See `debbugs-gnu-default-bug-number-list' for the default value.
> Will do both next days as time permits.
I've pushed this to the elpa repository, you might play with it. Within
a week or so, I will release debbugs 0.11.
>> Regards,
>> Tino
Best regards, Michael.
next prev parent reply other threads:[~2016-09-13 12:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 6:08 debbugs-0.10: two comments Tino Calancha
2016-09-12 7:05 ` Michael Albinus
2016-09-12 7:24 ` Tino Calancha
2016-09-12 7:32 ` Michael Albinus
2016-09-12 7:46 ` Tino Calancha
2016-09-13 12:06 ` Michael Albinus [this message]
2016-09-23 7:42 ` debbugs-0.10: doc fixes Tino Calancha
2016-09-23 12:40 ` Michael Albinus
2016-09-23 13:14 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760q0dmxh.fsf@gmx.de \
--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 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.