From: Avi Kivity <avi@redhat.com>
To: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
Cc: KVM list <kvm@vger.kernel.org>, kvm-ppc <kvm-ppc@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Alexander Graf <agraf@suse.de>, Paul Mackerras <paulus@samba.org>,
Carsten Otte <carsteno@de.ibm.com>,
"Roedel, Joerg" <Joerg.Roedel@amd.com>
Subject: Re: New git workflow
Date: Wed, 11 Apr 2012 09:42:22 +0000 [thread overview]
Message-ID: <4F8551FE.8010902@redhat.com> (raw)
In-Reply-To: <20120406210206.1ec352decb45d5035e9907d5@gmail.com>
On 04/06/2012 03:02 PM, Takuya Yoshikawa wrote:
> On Thu, 05 Apr 2012 20:02:44 +0300
> Avi Kivity <avi@redhat.com> wrote:
>
> > In a recent conversation, Linus persuaded me that it's time for change
> > in our git workflow; the following will bring it in line with the
> > current practices of most trees.
> >
> > The current 'master' branch will be abandoned (still available for
> > reviewing history). The new branch structure will be as follows:
>
> Please update Documentation/virtual/kvm/review-checklist.txt as well:
> 2. Patches should be against kvm.git master branch.
>
>
Yes, but let's wait a while until the workflow stabilizes.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
Cc: KVM list <kvm@vger.kernel.org>, kvm-ppc <kvm-ppc@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Alexander Graf <agraf@suse.de>, Paul Mackerras <paulus@samba.org>,
Carsten Otte <carsteno@de.ibm.com>,
"Roedel, Joerg" <Joerg.Roedel@amd.com>
Subject: Re: New git workflow
Date: Wed, 11 Apr 2012 12:42:22 +0300 [thread overview]
Message-ID: <4F8551FE.8010902@redhat.com> (raw)
In-Reply-To: <20120406210206.1ec352decb45d5035e9907d5@gmail.com>
On 04/06/2012 03:02 PM, Takuya Yoshikawa wrote:
> On Thu, 05 Apr 2012 20:02:44 +0300
> Avi Kivity <avi@redhat.com> wrote:
>
> > In a recent conversation, Linus persuaded me that it's time for change
> > in our git workflow; the following will bring it in line with the
> > current practices of most trees.
> >
> > The current 'master' branch will be abandoned (still available for
> > reviewing history). The new branch structure will be as follows:
>
> Please update Documentation/virtual/kvm/review-checklist.txt as well:
> 2. Patches should be against kvm.git master branch.
>
>
Yes, but let's wait a while until the workflow stabilizes.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-04-11 9:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 17:02 New git workflow Avi Kivity
2012-04-05 17:02 ` Avi Kivity
2012-04-06 12:02 ` Takuya Yoshikawa
2012-04-06 12:02 ` Takuya Yoshikawa
2012-04-11 9:42 ` Avi Kivity [this message]
2012-04-11 9:42 ` Avi Kivity
2012-04-08 11:33 ` Avi Kivity
2012-04-08 11:33 ` Avi Kivity
2012-04-11 12:23 ` Paul Mackerras
2012-04-11 12:23 ` Paul Mackerras
2012-04-11 19:50 ` Scott Wood
2012-04-11 19:50 ` Scott Wood
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=4F8551FE.8010902@redhat.com \
--to=avi@redhat.com \
--cc=Joerg.Roedel@amd.com \
--cc=agraf@suse.de \
--cc=carsteno@de.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=paulus@samba.org \
--cc=takuya.yoshikawa@gmail.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 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.