From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Laurent Desnogues <laurent.desnogues@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Switching to git
Date: Wed, 22 Apr 2009 10:50:37 -0400 [thread overview]
Message-ID: <20090422145037.GD3795@csclub.uwaterloo.ca> (raw)
In-Reply-To: <761ea48b0904220745i66d2e77cu90325fc1e004b3bb@mail.gmail.com>
On Wed, Apr 22, 2009 at 04:45:36PM +0200, Laurent Desnogues wrote:
> 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.
How does it make git not friendly? Commiting code that doesn't build
has always caused people pain, it just happens that with git it includes
the pain of loosing use of a major feature of git.
> And before someone jumps on me, I am not arguing against git, I start to
> like it.
I like the regex saerches in commits using git log. Having git-svn
to grab a svn tree and being able to do all the git tricks on it is
very handy. A native git tree is much faster to fetch though.
--
Len Sorensen
next prev parent reply other threads:[~2009-04-22 14:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 13:22 [Qemu-devel] Switching to git Anthony Liguori
2009-04-22 13:57 ` Kevin Wolf
2009-04-22 14:05 ` Anthony Liguori
2009-04-22 14:12 ` Gerd Hoffmann
2009-04-22 14:20 ` Laurent Desnogues
2009-04-22 14:22 ` Anthony Liguori
2009-04-22 14:37 ` Avi Kivity
2009-04-22 17:53 ` Andreas Färber
2009-04-22 18:09 ` Jamie Lokier
2009-04-22 18:13 ` Ryan Harper
2009-04-22 18:48 ` Avi Kivity
2009-04-22 14:38 ` Lennart Sorensen
2009-04-22 14:45 ` Laurent Desnogues
2009-04-22 14:50 ` Lennart Sorensen [this message]
2009-04-22 17:25 ` Johannes Schindelin
2009-04-22 17:49 ` Anthony Liguori
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=20090422145037.GD3795@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=aliguori@us.ibm.com \
--cc=laurent.desnogues@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).