From: "Chí-Thanh Christopher Nguyễn" <chithanh@gentoo.org>
To: gentoo-dev@lists.gentoo.org, x11 <x11@gentoo.org>
Subject: [gentoo-dev] Re: Better way to direct upstream bugs upstream?
Date: Sun, 30 Aug 2015 19:59:20 +0200 [thread overview]
Message-ID: <55E34478.6010605@gentoo.org> (raw)
In-Reply-To: <CAEdQ38F0y76kHiaZnQBYBmBVGcmekr1t7X3ZKgmJ6jec9w-tXg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Matt Turner schrieb:
> Worse, users sometimes file bugs in our bugzilla that we don't have time
> to respond to for a while during which time they're waiting on people
> without the ability to help them.
>
> Is there a better way of directing reporters to file bugs upstream? Of
> course it's not always clear whether a bug is an ebuild bug or something
> easily patched in Gentoo vs a driver bug that requires an upstream
> developer...
I think such bug reports are still useful. They can point to patches once
the issue has been resolved upstream, for consideration in a new ebuild
revision.
Whether they are kept open or resolved UPSTREAM while an upstream fix is
unavailable I have no strong opinion about.
Best regards,
Chí-Thanh Christopher Nguyễn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlXjRHgACgkQ+gvH2voEPRCiLwCeNOZAIpEsXwCIsSV2ZzMwXxO4
gUkAnR+5nwYhL8ty5YR2QoISDe4y+B8Y
=U/e0
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2015-08-30 17:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 19:53 [gentoo-dev] Better way to direct upstream bugs upstream? Matt Turner
2015-08-30 7:03 ` Kent Fredric
2015-08-30 7:20 ` Daniel Campbell
2015-08-30 7:54 ` Kent Fredric
2015-08-30 7:59 ` Daniel Campbell
2015-08-30 9:37 ` [gentoo-dev] " Duncan
2015-08-30 10:02 ` Kent Fredric
2015-09-02 19:17 ` Paweł Hajdan, Jr.
2015-09-03 9:32 ` Jason Zaman
2015-09-03 11:28 ` Kent Fredric
2015-09-03 20:16 ` Andrew Udvare
2015-09-07 19:51 ` Paweł Hajdan, Jr.
2015-09-07 23:47 ` Alec Warner
2015-08-30 12:15 ` [gentoo-dev] " Peter Stuge
2015-08-30 12:38 ` Kent Fredric
2015-08-30 17:59 ` Chí-Thanh Christopher Nguyễn [this message]
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=55E34478.6010605@gentoo.org \
--to=chithanh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=x11@gentoo.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