All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Lothian <mike@fireburn.co.uk>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: David Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] MAINTAINERS: update drm tree
Date: Fri, 6 Jul 2018 16:43:09 +0100	[thread overview]
Message-ID: <CAHbf0-Fq+4arPVG=+q1BoRCXowVNybACVJhy5J-60sJxfuPWDg@mail.gmail.com> (raw)
In-Reply-To: <CADnq5_NCN6jWVmDYwHtDgUCOFX1kTWAu36cRXVBxYJpyqtmy_w@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1850 bytes --]

Hi

Any change of this moving to https or the gitlab instance where its on as
default?

Cheers

Mike

On Fri, 6 Jul 2018 at 16:25 Alex Deucher <alexdeucher@gmail.com> wrote:

> On Fri, Jul 6, 2018 at 3:28 AM, Daniel Vetter <daniel.vetter@ffwll.ch>
> wrote:
> > Mail to dri-devel went out, linux-next was updated, but we forgot this
> > one here.
> >
> > Cc: David Airlie <airlied@linux.ie>
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
>
> Acked-by: Alex Deucher <alexander.deucher@amd.com>
>
> > ---
> >  MAINTAINERS | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 07d1576fc766..8edb34d28f23 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -581,7 +581,7 @@ W:  https://www.infradead.org/~dhowells/kafs/
> >
> >  AGPGART DRIVER
> >  M:     David Airlie <airlied@linux.ie>
> > -T:     git git://people.freedesktop.org/~airlied/linux (part of drm
> maint)
> > +T:     git git://anongit.freedesktop.org/drm/drm
> >  S:     Maintained
> >  F:     drivers/char/agp/
> >  F:     include/linux/agp*
> > @@ -4630,7 +4630,7 @@ F:        include/uapi/drm/vmwgfx_drm.h
> >  DRM DRIVERS
> >  M:     David Airlie <airlied@linux.ie>
> >  L:     dri-devel@lists.freedesktop.org
> > -T:     git git://people.freedesktop.org/~airlied/linux
> > +T:     git git://anongit.freedesktop.org/drm/drm
> >  B:     https://bugs.freedesktop.org/
> >  C:     irc://chat.freenode.net/dri-devel
> >  S:     Maintained
> > --
> > 2.18.0
> >
> > _______________________________________________
> > dri-devel mailing list
> > dri-devel@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/dri-devel
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
>

[-- Attachment #1.2: Type: text/html, Size: 3871 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-07-06 15:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06  7:28 [PATCH] MAINTAINERS: update drm tree Daniel Vetter
2018-07-06 15:24 ` Alex Deucher
2018-07-06 15:43   ` Mike Lothian [this message]
2018-07-09  7:37     ` Daniel Vetter
2018-07-09  9:38       ` Daniel Stone
2018-07-06 17:04 ` Rodrigo Vivi

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='CAHbf0-Fq+4arPVG=+q1BoRCXowVNybACVJhy5J-60sJxfuPWDg@mail.gmail.com' \
    --to=mike@fireburn.co.uk \
    --cc=airlied@linux.ie \
    --cc=alexdeucher@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@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.