Actually I just take a random guess each time of where to report to.
Also often I am offline, so queuing a mail to bugs.debian.org is quite
attractive.
On Mon, 04 Oct 2021 04:28:27 +0800
積丹尼 Dan Jacobson wrote:
>
> perltidy debian
> perltidy upstream
> bash-completion debian
> bash-completion upstream
Yeah, I know it's sometimes hard to tell where to submit bug reports
to. On the other hand, it looks like you are doing a good job of it.
Well OK. But e.g., if a user e.g., reports to all
perltidy debian
perltidy upstream
bash-completion debian
bash-completion upstream
then that would require a total of 4 x 4 = 16 cross references,
(as users have no hint of where to report.)
Control: forwarded -1 https://github.com/scop/bash-completion/issues/518
Control: tags -1 confirmed upstream fixed-upstream
Hello,
Hey, you could have mentioned that you submitted the bug upstream! :)
For future reference, here is is:
https://github.com/scop/bash-completion/issues/518
Package: bash-completion
Version: 1:2.11-3
Severity: minor
File: /usr/share/bash-completion/completions/perltidy
Only
$ perltidy -
works,
$ perltidy --
doesn't!
One needs to check the man page to see what the former mean.
5 matches
Mail list logo
