From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoffer Dall Subject: KVM/ARM Workflow Date: Sat, 26 Apr 2014 04:16:24 -0700 Message-ID: <20140426111624.GA36863@lvm> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org, Marc Zyngier To: kvmarm@lists.cs.columbia.edu Return-path: Received: from mail-la0-f50.google.com ([209.85.215.50]:41599 "EHLO mail-la0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751552AbaDZLQ2 (ORCPT ); Sat, 26 Apr 2014 07:16:28 -0400 Received: by mail-la0-f50.google.com with SMTP id gl10so238756lab.37 for ; Sat, 26 Apr 2014 04:16:26 -0700 (PDT) Content-Disposition: inline Sender: kvm-owner@vger.kernel.org List-ID: Hi all, Marc and I have been effectively co-maintained KVM/ARM 32-bit and 64-bit for a while, so we have sent a patch to make that official to the maintainers file. To make life easier for us and hopefully everybody else working on KVM/ARM, we have moved to using a single shared repo on kernel.org for all changes pending: https://git.kernel.org/cgit/linux/kernel/git/kvmarm/kvmarm.git/ We maintain three branches: * master: for fixes for the next -rcX release * next: for improvements for the next merge-window * queue: staging ground for things before they go into next Warning: queue is unstable, may rebase, break etc. at any time, so act accordingly. The branches track the equivalent patches with the same names in the kvm repository. Marc and I will take turn (in roughly 2-week stretches) to do the admin task of testing and applying patches to the repo. I have updated all documentation I could think of, but if I missed something, let me know. Thanks, -Christoffer