From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: Branch change for kvm tree
Date: Thu, 17 Dec 2020 08:14:05 +1100 [thread overview]
Message-ID: <20201217081405.212bacb7@canb.auug.org.au> (raw)
In-Reply-To: <c651fd52-e402-1474-38bc-6965470823cb@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 619 bytes --]
Hi Paolo,
On Wed, 16 Dec 2020 15:10:56 +0100 Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> 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?
Done.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-12-16 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 14:10 Branch change for kvm tree Paolo Bonzini
2020-12-16 21:14 ` Stephen Rothwell [this message]
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=20201217081405.212bacb7@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-next@vger.kernel.org \
--cc=pbonzini@redhat.com \
/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).