From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Thomas Piekarski <t.piekarski@deloquencia.de>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: Question about projects bugzilla and personal tags not being so personal
Date: Thu, 21 May 2020 22:21:47 +0200 [thread overview]
Message-ID: <CAKgNAkjyLhP8Qk=Bz5JyJVN1RTxGrgXaP8=R5gASw8zYvsZNUg@mail.gmail.com> (raw)
In-Reply-To: <228293bd-7d21-b08e-f7c4-c832e9c84dbb@deloquencia.de>
Hello Thomas,
On Thu, 21 May 2020 at 22:14, Thomas Piekarski
<t.piekarski@deloquencia.de> wrote:
>
> Hello,
>
>
> when skimming through the reported bugs at man-pages bugzilla I tried to
> tag a few bug reports with personal tags for my own workflow and own
> custom search filters (something like to_triage, to_ask and to_do).
>
> When I added one tag and saved that changes I got an:
>
> Changes submitted for bug 205763
> Email sent to:
> inout@users.sourceforge.net, on2014nm@gmail.com,
> zeno.endemann@googlemail.com
>
>
> Wondering, isn't the field personal tag meant only for me? I thought it
> should not sent out notifications. At least that is what the description
> of the field is saying. Am I doing something wrong here or do I have to
> configure something at my settings of bugzilla?
So, this is really a bugzilla question. I don't know the answer (I'm a
very simple user of bugzilla). It _may_ be that someone on this list
knows something about this, but you might best ask on a bugzilla
mailing list if you really need the answer.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-05-21 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 20:14 Question about projects bugzilla and personal tags not being so personal Thomas Piekarski
2020-05-21 20:21 ` Michael Kerrisk (man-pages) [this message]
2020-05-21 20:35 ` Thomas Piekarski
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='CAKgNAkjyLhP8Qk=Bz5JyJVN1RTxGrgXaP8=R5gASw8zYvsZNUg@mail.gmail.com' \
--to=mtk.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=t.piekarski@deloquencia.de \
/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.
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 NNTP newsgroup(s).