From: Kashyap Chamarthy <kchamart@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: Alistair Francis <alistair23@gmail.com>,
Cornelia Huck <cohuck@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: Migrating to the gitlab issue tracker
Date: Thu, 29 Oct 2020 18:36:57 +0100 [thread overview]
Message-ID: <20201029173657.7bar7sq6zzkeee2g@paraplu> (raw)
In-Reply-To: <3713093e-bf3b-bf23-a8d0-70fe429032ba@redhat.com>
On Thu, Oct 29, 2020 at 01:12:22PM -0400, John Snow wrote:
Hi,
[...]
> Mostly I was looking for any hard objections over the idea of issues not
> necessarily being sent to the list anymore, if there were any.
Not an objection, but I would miss discovering "interesting" issues by
virtue of bug emails sent to the list. Several times I've "stumbled
into" bugs on 'qemu-devel' that affect upper layers, or just Damn
Interesting QEMU Bugs™ (especially in the Block Layer) that helped me
gain better understanding, or something is already a "known issue".
That said, the reactions so far seem to be positive for moving to GitLab
Issues.
Maybe there are some acceptable workarounds. It looks like there's a
way to subscribe to GitLab issues via email[1]; and I can triage that
maildir as part of my regular email workflow.
https://docs.gitlab.com/ee/administration/incoming_email.html
[...]
--
/kashyap
next prev parent reply other threads:[~2020-10-29 17:37 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 16:01 Migrating to the gitlab issue tracker John Snow
2020-10-29 16:30 ` Daniel P. Berrangé
2020-10-29 16:41 ` Cornelia Huck
2020-10-29 16:49 ` Alistair Francis
2020-10-29 17:12 ` John Snow
2020-10-29 17:36 ` Kashyap Chamarthy [this message]
2020-10-29 19:55 ` Thomas Huth
2020-10-29 20:27 ` John Snow
2020-10-30 9:23 ` Daniel P. Berrangé
2020-10-30 10:03 ` Peter Maydell
2020-10-30 10:10 ` Daniel P. Berrangé
2020-10-30 10:57 ` Peter Maydell
2020-11-05 0:06 ` John Snow
2020-11-05 6:14 ` Thomas Huth
2020-11-05 9:54 ` Daniel P. Berrangé
2020-11-05 15:44 ` John Snow
2020-11-05 15:50 ` Daniel P. Berrangé
2020-11-08 9:00 ` Thomas Huth
2020-11-08 11:58 ` Peter Maydell
2020-11-09 8:04 ` Thomas Huth
2020-11-09 10:10 ` Daniel P. Berrangé
2020-11-09 10:14 ` Peter Maydell
2021-01-21 10:57 ` Thomas Huth
2021-01-21 16:20 ` John Snow
2020-10-30 10:26 ` Alex Bennée
2020-10-30 12:53 ` John Snow
2020-11-08 8:57 ` Thomas Huth
2020-10-29 18:04 ` John Snow
2020-10-29 20:33 ` Cornelia Huck
2020-10-30 9:16 ` Stefan Hajnoczi
2020-10-30 15:39 ` John Snow
2020-11-02 13:57 ` Laszlo Ersek
2020-11-02 14:26 ` Daniel P. Berrangé
2020-11-02 14:42 ` Eric Blake
2020-11-04 17:10 ` Laszlo Ersek
2020-11-04 17:03 ` Laszlo Ersek
2020-11-04 17:19 ` Daniel P. Berrangé
2020-11-06 15:37 ` Laszlo Ersek
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=20201029173657.7bar7sq6zzkeee2g@paraplu \
--to=kchamart@redhat.com \
--cc=alistair23@gmail.com \
--cc=cohuck@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.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).