I don't see why this is not clear. Bug reports that have been sent to
upstream are marked with proof that they have been sent upstream.
___
devscripts-devel mailing list
devscripts-devel@lists.alioth.debian.org
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
Processing commands for cont...@bugs.debian.org:
> tags 807810 + moreinfo
Bug #807810 [devscripts] Mention what if one wants to mark the bug forwarded to
more than one place
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
807810:
Processing commands for cont...@bugs.debian.org:
> tags 807810 - moreinfo
Bug #807810 [devscripts] Mention what if one wants to mark the bug forwarded to
more than one place
Removed tag(s) moreinfo.
> reassign 807810 bugs.debian.org
Bug #807810 [devscripts] Mention what if one wants to mark the
___
devscripts-devel mailing list
devscripts-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/devscripts-devel
On Sun, 2015-12-13 at 11:34 +, Nicholas Bamber wrote:
> I don't see why this is not clear. Bug reports that have been sent to
> upstream are marked with proof that they have been sent upstream.
nn@bugs doesn't reach the submitter by default. If you want them to
answer a question, then
