public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Willy Tarreau <willy@w.ods.org>
Cc: Paul Jackson <pj@sgi.com>, jes@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: git for dummies, anyone? (was: Re: How in tarnation do I git v2.6.16-rc2?  hg died and I still don't git git)
Date: Fri, 10 Feb 2006 09:08:42 -0500	[thread overview]
Message-ID: <20060210140842.GA18707@thunk.org> (raw)
In-Reply-To: <20060210062309.GA22620@w.ods.org>

On Fri, Feb 10, 2006 at 07:23:09AM +0100, Willy Tarreau wrote:
> I did the opposite : I tried hg as soon as Matt announced it, but I
> got lost in the "python dumps" which appeared at the slightest error,
> because I did not understand what the problem was. Then I tried git,
> at least to be able to keep in sync with Marcelo. With git, I had
> some opportunities to catch some understandable error messages spit
> out of some shell scripts even when not caught by the script itself.
> But using it less than twice a week requires me to read the manual
> again before doing anything useful :-(

Mercurial has gotten a lot better about "python dumps" as a signal
that you had typed something wrong, or had permissions problems, etc.
I got annoyed about that too, but I just learned to ignore them and
assume that 90% of the time, it was due to a mistake on my end.
Things are a lot better there; claiming mercurial sucks for its early
rough edges is about as far as claiming that git sucks because its
performance sucked rocks on laptop drives in its early days before
Linus added support for packs.  

						- Ted

      reply	other threads:[~2006-02-10 14:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08 15:03 How in tarnation do I git v2.6.16-rc2? hg died and I still don't git git Paul Jackson
2006-02-08 15:14 ` Dale Farnsworth
2006-02-08 15:27   ` Paul Jackson
2006-02-08 15:15 ` Mattia Dongili
     [not found] ` <20060208101626.3afa69ba.seanlkml@sympatico.ca>
2006-02-08 15:16   ` sean
2006-02-08 17:53 ` Bryan O'Sullivan
2006-02-08 18:06   ` Paul Jackson
2006-02-09 13:08 ` git for dummies, anyone? (was: Re: How in tarnation do I git v2.6.16-rc2? hg died and I still don't git git) Jes Sorensen
2006-02-09 14:17   ` git for dummies, anyone? Jeff Garzik
2006-02-09 14:36     ` Josh Boyer
2006-02-09 14:43     ` Jes Sorensen
2006-02-09 14:55     ` Paul Jackson
2006-02-09 16:46       ` Catalin Marinas
2006-02-09 15:35     ` Diego Calleja
2006-02-09 15:56       ` Jes Sorensen
2006-02-09 16:07       ` J. Bruce Fields
2006-02-09 16:37       ` Marc Koschewski
2006-02-09 14:50   ` git for dummies, anyone? (was: Re: How in tarnation do I git v2.6.16-rc2? hg died and I still don't git git) Paul Jackson
2006-02-09 23:16     ` Willy Tarreau
2006-02-10  0:03       ` Paul Jackson
2006-02-10  6:23         ` Willy Tarreau
2006-02-10 14:08           ` Theodore Ts'o [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=20060210140842.GA18707@thunk.org \
    --to=tytso@mit.edu \
    --cc=jes@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.com \
    --cc=willy@w.ods.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