qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH] MAINTAINERS: Update 9pfs tree URL
Date: Wed, 27 Jan 2021 15:33:51 +0100	[thread overview]
Message-ID: <1679340.e36fRnoiaZ@silver> (raw)
In-Reply-To: <2867808.c4G3KLOmWt@silver>

On Freitag, 15. Januar 2021 14:50:17 CET Christian Schoenebeck wrote:
> On Freitag, 15. Januar 2021 14:42:24 CET Greg Kurz wrote:
> > I've already moved my repositories to gitlab for extra CI coverage,
> > and I won't use the ones at github anymore.
> > 
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> 
> Reviewed-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
> 
> > ---
> > 
> >  MAINTAINERS |    2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index cb0656aec3d4..21038d3fdfce 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -1828,7 +1828,7 @@ X: hw/9pfs/xen-9p*
> > 
> >  F: fsdev/
> >  F: docs/interop/virtfs-proxy-helper.rst
> >  F: tests/qtest/virtio-9p-test.c
> > 
> > -T: git https://github.com/gkurz/qemu.git 9p-next
> > +T: git https://gitlab.com/gkurz/qemu.git 9p-next
> > 
> >  virtio-blk
> >  M: Stefan Hajnoczi <stefanha@redhat.com>

What's the status of this patch? I would add my T: line below just for the 
records. But I'd rather wait for this patch being merged to main line.

Best regards,
Christian Schoenebeck




  reply	other threads:[~2021-01-27 14:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 13:42 [PATCH] MAINTAINERS: Update 9pfs tree URL Greg Kurz
2021-01-15 13:50 ` Christian Schoenebeck
2021-01-27 14:33   ` Christian Schoenebeck [this message]
2021-01-27 16:02     ` Greg Kurz
2021-01-27 16:07       ` Laurent Vivier
2021-01-27 16:39         ` Christian Schoenebeck

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=1679340.e36fRnoiaZ@silver \
    --to=qemu_oss@crudebyte.com \
    --cc=groug@kaod.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).