All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Adam Jackson <ajax@redhat.com>
Cc: "DRM maintainer tools announcements, discussion,
	and development" <dim-tools@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>,
	IGT development <igt-dev@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [igt-dev] RFC: Migration to Gitlab
Date: Wed, 22 Aug 2018 09:06:45 -0700	[thread overview]
Message-ID: <20180822160645.GC2340@intel.com> (raw)
In-Reply-To: <7393f5fe500ab7173ec579d45866b4506c86ffd7.camel@redhat.com>

On Wed, Aug 22, 2018 at 10:19:19AM -0400, Adam Jackson wrote:
> On Wed, 2018-08-22 at 16:13 +0300, Jani Nikula wrote:
> 
> > - Sticking to fdo bugzilla and disabling gitlab issues for at least
> >   drm-intel for the time being. Doing that migration in the same go is a
> >   bit much I think. Reassignment across bugzilla and gitlab will be an
> >   issue.
> 
> Can you elaborate a bit on the issues here? The actual move-the-bugs
> process has been pretty painless for the parts of xorg we've done so
> far.

I guess there is nothing against moving the bugs there. The concern is only on
doing everything at once.

I'm in favor of moving gits for now and after we are confident that
everything is there and working we move the bugs.

One question about the bugzilla:

Will all the referrences on all commit messages get outdated after
bugzilla is dead?
Or bugzilla will stay up for referrence but closed for interaction?
or all old closed stuff are always moved and bugzilla.fd.o as well and
bugzilla.fd.o will be mirroring gitlab?

Thanks,
Rodrigo.

> 
> - ajax
> _______________________________________________
> dim-tools mailing list
> dim-tools@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dim-tools
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Adam Jackson <ajax@redhat.com>
Cc: "DRM maintainer tools announcements, discussion,
	and development" <dim-tools@lists.freedesktop.org>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>,
	IGT development <igt-dev@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [igt-dev] RFC: Migration to Gitlab
Date: Wed, 22 Aug 2018 09:06:45 -0700	[thread overview]
Message-ID: <20180822160645.GC2340@intel.com> (raw)
In-Reply-To: <7393f5fe500ab7173ec579d45866b4506c86ffd7.camel@redhat.com>

On Wed, Aug 22, 2018 at 10:19:19AM -0400, Adam Jackson wrote:
> On Wed, 2018-08-22 at 16:13 +0300, Jani Nikula wrote:
> 
> > - Sticking to fdo bugzilla and disabling gitlab issues for at least
> >   drm-intel for the time being. Doing that migration in the same go is a
> >   bit much I think. Reassignment across bugzilla and gitlab will be an
> >   issue.
> 
> Can you elaborate a bit on the issues here? The actual move-the-bugs
> process has been pretty painless for the parts of xorg we've done so
> far.

I guess there is nothing against moving the bugs there. The concern is only on
doing everything at once.

I'm in favor of moving gits for now and after we are confident that
everything is there and working we move the bugs.

One question about the bugzilla:

Will all the referrences on all commit messages get outdated after
bugzilla is dead?
Or bugzilla will stay up for referrence but closed for interaction?
or all old closed stuff are always moved and bugzilla.fd.o as well and
bugzilla.fd.o will be mirroring gitlab?

Thanks,
Rodrigo.

> 
> - ajax
> _______________________________________________
> dim-tools mailing list
> dim-tools@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dim-tools
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2018-08-22 16:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 11:44 RFC: Migration to Gitlab Daniel Vetter
2018-08-22 11:44 ` [igt-dev] " Daniel Vetter
     [not found] ` <CAKMK7uFciLYN2G+VqvAwk5D9+H5dw6Tb5FtmWgxCnWtLa0uOEg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-08-22 13:05   ` [Intel-gfx] " Sean Paul
2018-08-22 13:05     ` [igt-dev] " Sean Paul
2018-08-22 13:13 ` [igt-dev] " Jani Nikula
2018-08-22 13:13   ` [Intel-gfx] " Jani Nikula
2018-08-22 14:19   ` Adam Jackson
2018-08-22 14:19     ` Adam Jackson
2018-08-22 16:06     ` Rodrigo Vivi [this message]
2018-08-22 16:06       ` Rodrigo Vivi
2018-08-22 16:37       ` Daniel Stone
2018-08-22 16:37         ` Daniel Stone
     [not found]         ` <CAPj87rNH+rLZexK3QoqzeBLZPr5QYtAz187NbKN5JUFnzxoxHg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-08-22 17:01           ` Rodrigo Vivi
2018-08-22 17:01             ` Rodrigo Vivi
     [not found]       ` <20180822160645.GC2340-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-08-24  6:52         ` Jani Nikula
2018-08-24  6:52           ` Jani Nikula
2018-08-24 12:03           ` Daniel Vetter
2018-08-24 12:03             ` Daniel Vetter
2018-08-22 14:44   ` Daniel Vetter
2018-08-22 14:44     ` Daniel Vetter
     [not found]     ` <CAKMK7uG7Hs+MooCu4Fid=20J0EfsPakvWD6MtkcQ0RTBuR3G5Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-08-22 16:33       ` Daniel Stone
2018-08-22 16:33         ` Daniel Stone
2018-08-22 15:02 ` Emil Velikov
2018-08-22 15:02   ` [igt-dev] " Emil Velikov
2018-08-22 16:29   ` Daniel Stone
2018-08-22 16:29     ` [igt-dev] " Daniel Stone
2018-08-23 17:29     ` Visibility of issues fd.o admins are faced with (Was: Re: RFC: Migration to Gitlab) Emil Velikov

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=20180822160645.GC2340@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=ajax@redhat.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.