From: Samuel Bernardo <samuelbernardo.mail@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 0/1] remove EGO_VENDOR support from go-module.eclass
Date: Tue, 12 May 2020 18:36:42 +0100 [thread overview]
Message-ID: <64528660-8936-d788-1e0e-dedceb731ed1@gmail.com> (raw)
In-Reply-To: <20200512153847.GB8790@linux1.home>
[-- Attachment #1.1: Type: text/plain, Size: 990 bytes --]
Hi William,
On 5/12/20 4:38 PM, William Hubbs wrote:
> Hi Samuel,
>
> this change will apply to all users of the eclass.
>
> Overlays are not considered blockers for in-tree eclass work.
>
> Also, keepin mind that there was a qa warning in place for this issue
> for 3 months, so overlay owners should have been able to see that and
> migrate their ebuilds to EGO_SUM.
Yes, I confirm that I'm aware of that. Thank you for your good work!
> That being said, if any overlay owner would like my assistance with
> migrating their ebuilds, I have no problem with showing them how.
No problem from my side, I have already do that.
My concern was about the others, for instance go-overlay that I have
enabled.
Should it be possible to run a QA check to create a bug request to
remember the update of those ebuilds in the overlays?
This would reduce the bug management task when searching for related bugs.
> Thanks,
>
> William
Thanks,
Samuel
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-12 17:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 21:16 [gentoo-dev] [PATCH 0/1] remove EGO_VENDOR support from go-module.eclass William Hubbs
2020-05-10 21:16 ` [gentoo-dev] [PATCH 1/1] eclass/go-module.eclass: remove EGO_VENDOR support William Hubbs
2020-05-11 13:51 ` [gentoo-dev] [PATCH 0/1] remove EGO_VENDOR support from go-module.eclass Mike Gilbert
2020-05-11 16:13 ` David Seifert
2020-05-11 18:54 ` William Hubbs
2020-05-11 22:58 ` William Hubbs
2020-05-12 13:59 ` Mike Gilbert
2020-05-11 22:45 ` Andreas K. Hüttel
2020-05-11 23:00 ` William Hubbs
2020-05-12 5:47 ` Matt Turner
2020-05-12 15:29 ` William Hubbs
2020-05-12 10:41 ` Samuel Bernardo
2020-05-12 15:38 ` William Hubbs
2020-05-12 17:36 ` Samuel Bernardo [this message]
2020-05-12 17:40 ` Joonas Niilola
2020-05-12 18:51 ` Samuel Bernardo
2020-06-12 20:55 ` William Hubbs
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=64528660-8936-d788-1e0e-dedceb731ed1@gmail.com \
--to=samuelbernardo.mail@gmail.com \
--cc=gentoo-dev@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