I am just saying that via a mechanical reading of the documents, one
cannot tell which items only allow / should have one vs. more arguments.
I just wish the docs would say how many.
JM> That being said, it has already been shown the "address" part of the
JM> command can be arbitrary text, so you
On Mon, Dec 21, 2015 at 12:54:40AM +0800, 積丹尼 Dan Jacobson wrote:
> By the way one might be surprised that there could be two of these
>
> $ w3m -dump http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718840 | grep
> Found
> Found in versions apt-show-versions/0.22.1, apt-show-versions/0.22.7
>
By the way one might be surprised that there could be two of these
$ w3m -dump http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718840 | grep Found
Found in versions apt-show-versions/0.22.1, apt-show-versions/0.22.7
based on
found bug [version]
Indicate that a bug was found
On Dec 13, 2015 6:06 AM, "積丹尼 Dan Jacobson" wrote:
>forwarded bug address
>Mark the bug as forwarded to the given address (usually an
email
>address or a URL for an upstream bug tracker).
>
> Mention what if one wants to mark the bug forwarded
James,
I agree that I can see no need to support multiple forwarding
addresses. However it turns out we currently support that. As a test
this bug has been forwarded to two locations.
Currently this bug is asking for that to be documented.
On 17/12/15 14:17, James McCoy
On Dec 17, 2015 12:57 PM, "Nicholas Bamber" wrote:
>
> James,
> I agree that I can see no need to support multiple forwarding
addresses. However it turns out we currently support that.
If by "support", you mean we don't do any verification of what the
"forwarded"
On 17/12/15 19:29, James McCoy wrote:
On Dec 17, 2015 12:57 PM, "Nicholas Bamber" > wrote:
>
> James,
> I agree that I can see no need to support multiple forwarding
addresses. However it turns out we currently support that.
If
reassign 807810 bugs.debian.org
thanks
OK I'll reassign this bug, in the hope that on
https://www.debian.org/Bugs/server-control they will add some policy
statement about what to do when one wants to mark a bug forwarded to
more than one place, for whatever unexpected reason that might come up.
I don't think that quite follows. I was not suggesting that
bugs.debian.org change anything. But they might lock it down in the
future. So if we document precisely how things work now we would be
overdocumenting the system.
On 17/12/15 23:05, 積丹尼 Dan Jacobson wrote:
reassign 807810
> "NB" == Nicholas Bamber writes:
NB> I don't think that quite follows. I was not suggesting that
NB> bugs.debian.org change anything. But they might lock it down in the
NB> future. So if we document precisely how things work now we would be
NB> overdocumenting the
Package: devscripts
Version: 2.15.9
Severity: wishlist
File: /usr/share/man/man1/bts.1.gz
forwarded bug address
Mark the bug as forwarded to the given address (usually an email
address or a URL for an upstream bug tracker).
Mention what if one wants to mark the bug
11 matches
Mail list logo