All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: RfC: MAINTAINERS update for qemu drm drivers.
Date: Mon, 21 Nov 2016 20:22:34 +0100	[thread overview]
Message-ID: <1479756154.9742.57.camel@redhat.com> (raw)
In-Reply-To: <20161121190538.3afw56l3nwbicjtf@phenom.ffwll.local>

  Hi,

> Also I think one shared git repo for all of them would be
> good.

Yep, I'm doing that (see today's drm-qemu pull req @ dri-devel).
But, yes, I can place the git repo link in MAINTAINERS too.

cheers,
  Gerd

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

WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Qemu-devel] RfC: MAINTAINERS update for qemu drm drivers.
Date: Mon, 21 Nov 2016 20:22:34 +0100	[thread overview]
Message-ID: <1479756154.9742.57.camel@redhat.com> (raw)
In-Reply-To: <20161121190538.3afw56l3nwbicjtf@phenom.ffwll.local>

  Hi,

> Also I think one shared git repo for all of them would be
> good.

Yep, I'm doing that (see today's drm-qemu pull req @ dri-devel).
But, yes, I can place the git repo link in MAINTAINERS too.

cheers,
  Gerd

  reply	other threads:[~2016-11-21 19:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21 18:24 RfC: MAINTAINERS update for qemu drm drivers Gerd Hoffmann
2016-11-21 18:24 ` [Qemu-devel] " Gerd Hoffmann
2016-11-21 19:05 ` Daniel Vetter
2016-11-21 19:05   ` [Qemu-devel] " Daniel Vetter
2016-11-21 19:22   ` Gerd Hoffmann [this message]
2016-11-21 19:22     ` Gerd Hoffmann

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=1479756154.9742.57.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=qemu-devel@nongnu.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.