On 9/24/19 11:40 PM, Matt Turner wrote:
On Wed, Sep 11, 2019 at 9:14 PM Kyle Brenneman <kbrenne...@nvidia.com> wrote:
On 9/9/19 12:07 PM, Adam Jackson wrote:
On Wed, 2019-09-04 at 14:27 -0600, Kyle Brenneman wrote:
On 9/4/19 8:44 AM, Daniel Stone wrote:
Hi,
On Wed, 4 Sep 2019 at 15:12, Chuck Atkins <chuck.atk...@kitware.com> wrote:
Can we use Gitlab's GitHub import feature?
https://gitlab.freedesktop.org/help/user/project/import/github.md
I haven't used it before but it looks like it will migrate everything, i.e.
repo, issues, prs, etc.
Yeah, we definitely can. We can create a new namespace for GLVND and
import the project into there.
Who else should I add to the group?
I'm not very familiar with the administrative side of GitLab -- does
adding to the group just control who can check in new commits?
It's fairly fine-grained, for details see:
https://docs.gitlab.com/ee/user/permissions.html
- ajax
In that case, in addition to myself and the other NVIDIA engineers, Adam
Jackson would probably make sense to add for push/merge permission. Not
sure who else.
Is there anything that's needed from me to get the GitHub repo ready to
import?
-Kyle
Okay, everyone is in agreement. Great!
Mesa 19.2.0 is going to be released tomorrow and has been prepared for
libglvnd finally having pkgconfig files after many years of waiting,
but there's no libglvnd release for distros to ship. Is there
something we're waiting on?
Can we make a release, transition to FDO Gitlab, etc? Daniel says that
only someone with permissions on the GitHub repo (Kyle, I suppose) can
do the transition.
Can we please make this happen tomorrow?
I just updated the libglvnd package version to 1.2.0, and tagged it as a
new release.
As for migrating the repository, what do I need to do to do that?
-Kyle
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
