Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: Takashi Iwai <tiwai@suse.de>,
	ALSA development <alsa-devel@alsa-project.org>
Subject: Re: HG vs GIT
Date: Thu, 7 Feb 2008 19:27:48 +0000	[thread overview]
Message-ID: <20080207192747.GA30831@sirena.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.58.0802070759200.9968@shell4.speakeasy.net>

On Thu, Feb 07, 2008 at 08:03:57AM -0800, Trent Piepho wrote:
> On Thu, 7 Feb 2008, Mark Brown wrote:

> > Judging from what I've seen on the IRC channels I hang around on I get
> > the impression that relatively few people doing this on a user level
> > (typically people with shiny new laptops and so on) are using hg to
> > access the drivers - they mostly seem to be using either the snapshot or

> grab the code from Hg.  Certainly a lot of people just grab the tip tarball
> with wget and don't use hg clone, but they have the same codebase that
> developers using Hg have.

Sure, that's my point, pretty much - for a user grabbing a tarball it's
immaterial where the contents of the taball come from so long as they
correspond to the software they want.  A change from hg to git wouldn't
affect them so long as the tarballs continue to be provided and provide
access to current ALSA code.

If your concern is more that people using the tarball will be using it
in combination with an unknown distribution kernel rather than the rest
of the tree (assuming ALSA decides to change to git and go for a full
kernel tree, which I hope happens) then surely this isn't much of a
change from the current situation?

  reply	other threads:[~2008-02-07 19:27 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07  9:37 HG vs GIT Jaroslav Kysela
2008-02-07 11:27 ` Takashi Iwai
2008-02-07 11:45   ` Andrew Paprocki
2008-02-07 12:03     ` Takashi Iwai
2008-02-07 12:19       ` Jaroslav Kysela
2008-02-07 15:13         ` Takashi Iwai
2008-02-07 13:10       ` Trent Piepho
2008-02-07 13:26         ` Takashi Iwai
2008-02-07 13:41           ` Trent Piepho
2008-02-07 13:48             ` Takashi Iwai
2008-02-07 13:52               ` Jaroslav Kysela
2008-02-07 14:05                 ` Takashi Iwai
2008-02-07 14:07                   ` Jaroslav Kysela
2008-02-07 15:49                   ` Trent Piepho
2008-02-07 16:03                     ` Takashi Iwai
2008-02-07 19:46                       ` Mark Brown
2008-02-07 20:36                         ` Takashi Iwai
2008-02-08  0:42                           ` Mark Brown
2008-02-08  1:09                             ` Tobin Davis
2008-02-07 14:49               ` Tobin Davis
2008-02-07 15:00         ` Mark Brown
2008-02-07 15:18           ` Takashi Iwai
2008-02-07 16:03           ` Trent Piepho
2008-02-07 19:27             ` Mark Brown [this message]
2008-02-10 20:17         ` AK4114 - listing regs in proc - PATCH Pavel Hofman
2008-02-11 13:47           ` Takashi Iwai
2008-02-07 15:22       ` HG vs GIT Timur Tabi
2008-02-07 16:09         ` Takashi Iwai
2008-02-07 12:03   ` Jaroslav Kysela
2008-02-07 21:14   ` Rene Herman
2008-02-07 11:39 ` Mark Brown
2008-02-07 13:06 ` James Courtier-Dutton
2008-02-07 15:20 ` Timur Tabi
2008-02-07 15:53 ` Clemens Ladisch
2008-02-07 21:12 ` Rene Herman

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=20080207192747.GA30831@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    --cc=xyzzy@speakeasy.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