From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LwdiH-0002Uh-1c for qemu-devel@nongnu.org; Wed, 22 Apr 2009 10:46:13 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LwdiC-0002Sx-0Z for qemu-devel@nongnu.org; Wed, 22 Apr 2009 10:46:12 -0400 Received: from [199.232.76.173] (port=53999 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LwdiB-0002Sr-RQ for qemu-devel@nongnu.org; Wed, 22 Apr 2009 10:46:07 -0400 Received: from mail-fx0-f219.google.com ([209.85.220.219]:56285) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LwdiB-00073a-F9 for qemu-devel@nongnu.org; Wed, 22 Apr 2009 10:46:07 -0400 Received: by fxm19 with SMTP id 19so284201fxm.34 for ; Wed, 22 Apr 2009 07:46:06 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20090422143855.GC3795@csclub.uwaterloo.ca> References: <49EF1A26.70007@us.ibm.com> <761ea48b0904220720h48a3c53cv9f90a3c94a31f5d5@mail.gmail.com> <20090422143855.GC3795@csclub.uwaterloo.ca> Date: Wed, 22 Apr 2009 16:45:36 +0200 Message-ID: <761ea48b0904220745i66d2e77cu90325fc1e004b3bb@mail.gmail.com> Subject: Re: [Qemu-devel] Switching to git From: Laurent Desnogues Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Lennart Sorensen Cc: Anthony Liguori , "qemu-devel@nongnu.org" On Wed, Apr 22, 2009 at 4:38 PM, Lennart Sorensen wrote: > On Wed, Apr 22, 2009 at 04:20:44PM +0200, Laurent Desnogues wrote: >> And what for people between users and maintainers, for instance those >> who propose patches? =A0Will there be some recommendations on how >> to post patches so that it works well? =A0And don't forget that for some >> people just telling "a set of patches is good as long as it can be >> bisected" is too short :-) > > Commits that can be bisected is very appreciated. =A0I have hit way too > many commits in qemu that cause build failures, segfaults, etc, and just > generally make bisecting a major pain. I certainly wasn't arguing against bisectability :) I just wanted to be sure how to achieve it would be described somewhere to help git newcomers. I used that as an example of what makes git not very user friendly, like inventing some new terminology or use new command names for things that have been used for years. And before someone jumps on me, I am not arguing against git, I start to like it. Laurent