public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] libGL symlinks vs `eselect opengl`
Date: Sun, 23 Dec 2018 18:12:34 +0300	[thread overview]
Message-ID: <20181223181234.4f015dbc69074e06d3e4272d@gentoo.org> (raw)
In-Reply-To: <CAJjP=BsCFPMCnrS02bFvubMx5Xmy3oveJF7+qps0SA6OE5_07Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]

Hi,

Sorry, for delay, but maybe reply will be still useful.

On Wed, 29 Aug 2018 20:20:29 +0200 Davyd McColl wrote:
> Thanks for getting back to me. I'd really like to not make a useless bug
> report, so please bear with me:
> 
> 1. Am I correct that I should report here:
> https://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%20Linux

Yes.

> 2. I ask the above because I'm not entirely clear on how to CC opengl and
> celestia at the above url. If that's the right place (and it looks to be
> right), please let me know how to apply the correct CCs such that the right
> people get eyes on this and I'm not spamming the wrong people (:

Assign to celestia, CC opengl. This is not mandatory, since all new
bugs are reviewed by bug wranglers and assigned as appropriate.

Please be sure to provide emerge --info output and how celestia and
opengl are configured on your system, e.g. eix output or emerge -pv
output for corresponding packages.

Best regards,
Andrew Savchenko

[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-12-23 15:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 18:33 [gentoo-user] libGL symlinks vs `eselect opengl` Davyd McColl
2018-08-29 16:19 ` Andrew Savchenko
2018-08-29 18:20   ` Davyd McColl
2018-12-23 15:12     ` Andrew Savchenko [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=20181223181234.4f015dbc69074e06d3e4272d@gentoo.org \
    --to=bircoph@gentoo.org \
    --cc=gentoo-user@lists.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