From: Greg KH <gregkh@linuxfoundation.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: Feeding bugzilla.kernel.org USB component to the linux-usb list
Date: Sat, 9 Nov 2019 10:23:46 +0100 [thread overview]
Message-ID: <20191109092346.GF1293712@kroah.com> (raw)
In-Reply-To: <20191106210455.hpe63idbcz3yw54z@chatter.i7.local>
On Wed, Nov 06, 2019 at 04:04:55PM -0500, Konstantin Ryabitsev wrote:
> Hi, all:
>
> I noticed that Greg has an auto-reply for any new bugs opened on
> bugzilla.kernel.org for the USB component:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=205449
>
> Would it make more sense to feed those into the mailing list instead of
> asking bug submitters to send a new email? Anyone responding to the bugmail
> sent to the list will be properly recorded in the bug comments (and if they
> don't have an account on bugzilla.kernel.org, a stub account will be
> automatically created).
>
> It seems like that would be a friendlier setup that doesn't require bug
> submitters to do any more work, but I leave it up to you. This scheme is
> already used by other projects, e.g.:
> https://lore.kernel.org/linux-xfs/bug-202349-201763@https.bugzilla.kernel.org%2F/
>
> You can see Dave Chinner replying to bugmail directly and it being recorded
> in the bug entry:
> https://lore.kernel.org/linux-xfs/20190124233132.GO4205@dastard/
> https://bugzilla.kernel.org/show_bug.cgi?id=202349#c7
>
> Please let me know if that's something you would like.
Yeah, I guess it's about time to just set up the feed to do that, thanks
for bringing it up again, I had forgotten about it.
thanks,
greg k-h
next prev parent reply other threads:[~2019-11-09 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 21:04 Feeding bugzilla.kernel.org USB component to the linux-usb list Konstantin Ryabitsev
2019-11-09 9:23 ` Greg KH [this message]
2019-11-11 20:40 ` Konstantin Ryabitsev
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=20191109092346.GF1293712@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
/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).