All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
	James Courtier-Dutton <James@superbug.co.uk>,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: alsa cvs broken
Date: Mon, 03 Apr 2006 18:05:32 +0200	[thread overview]
Message-ID: <443147CC.40905@keyaccess.nl> (raw)
In-Reply-To: <Pine.LNX.4.61.0604031458460.9509@tm8103.perex-int.cz>

Jaroslav Kysela wrote:

> I must say that git looks too much "kernel" oriented and sometimes 
> hard-to-use. Mercurial has my sympatics, because it uses Python (on
> other hand, it might imply some performance issues).
> 
> I would start with mercurial and we'll see then.

Mind a vote against mercurial, and for GIT? Not because I think GIT is 
necesarily (and at the moment) better -- I in fact don't know either yet 
in any detail.

GIT is the kernel SCM though and unless it's really significantly worse, 
I believe it's better to simply use it. I've been looking to get into 
ALSA a bit for example, and I'd really not appreciate having to learn 
yet another SCM when I'm going to be making use of GIT for all the other 
kernel stuff anyway.

GIT is also still picking up speed. Keith Packard was even converting X 
CVS for example. Mercurial might be good I guess, but it's also very 
likely going to be one of those "oh no, not yet another" ones, maybe 
even keeping potential developers away.

Rene.


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

  parent reply	other threads:[~2006-04-03 16:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-03 11:18 alsa cvs broken James Courtier-Dutton
2006-04-03 12:07 ` Takashi Iwai
2006-04-03 12:21   ` James Courtier-Dutton
2006-04-03 12:39     ` Jaroslav Kysela
2006-04-03 12:53       ` Takashi Iwai
2006-04-03 13:08         ` Jaroslav Kysela
2006-04-03 13:13           ` Takashi Iwai
2006-04-03 13:22             ` Jaroslav Kysela
2006-04-03 13:31               ` Takashi Iwai
2006-04-03 13:47             ` James Courtier-Dutton
2006-04-03 13:51               ` Jaroslav Kysela
2006-04-03 16:05           ` Rene Herman [this message]
2006-04-03 16:15             ` Takashi Iwai
2006-04-05 11:05               ` Jaroslav Kysela
2006-04-05 11:20                 ` Takashi Iwai
2006-04-05 11:54                   ` James Courtier-Dutton
2006-04-05 18:04                   ` Rene Herman
2006-04-07 13:03                     ` Takashi Iwai
2006-04-03 12:30   ` Adrian McMenamin
2006-04-03 12:44     ` Takashi Iwai
2006-04-03 12:46       ` Adrian McMenamin
2006-04-03 12:51         ` Takashi Iwai

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=443147CC.40905@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=James@superbug.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=perex@suse.cz \
    --cc=tiwai@suse.de \
    /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.