linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Branch change for kvm tree
Date: Wed, 16 Dec 2020 15:10:56 +0100	[thread overview]
Message-ID: <c651fd52-e402-1474-38bc-6965470823cb@redhat.com> (raw)

Hi Stephen,

linux-next is currently using kvm.git's "linux-next" branch. 
Unfortunately I have just learnt of this fact; KVM maintainers and 
developers have always used the "next" branch instead.

It seems like until a few months ago "linux-next" was a symbolic link to 
the "next" branch, but something must have changed since then on the 
kernel.org side and thus the branch is frozen to last August.

Would you please make the change to kvm.git's "next" branch?

Thanks,

Paolo


             reply	other threads:[~2020-12-16 14:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 14:10 Paolo Bonzini [this message]
2020-12-16 21:14 ` Branch change for kvm tree Stephen Rothwell

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=c651fd52-e402-1474-38bc-6965470823cb@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).