From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Trent Piepho <xyzzy@speakeasy.org>
Subject: Re: HG vs GIT
Date: Thu, 07 Feb 2008 16:18:19 +0100 [thread overview]
Message-ID: <s5hzlucyev8.wl%tiwai@suse.de> (raw)
In-Reply-To: <20080207150022.GA8453@rakim.wolfsonmicro.main>
At Thu, 7 Feb 2008 15:00:22 +0000,
Mark Brown wrote:
>
> On Thu, Feb 07, 2008 at 05:10:27AM -0800, Trent Piepho wrote:
> > On Thu, 7 Feb 2008, Takashi Iwai wrote:
>
> > > Right, if you are a developer, it's fine (and even better). But, my
> > > concern is that the whole linux kernel tree might be too heavy for
> > > some casual user who just wants to try the latest version of ALSA
> > > driver... "Download 50MB and use 350MB disk space just for a single
> > > fix? Hell, no!"
>
> > You'll certainly get a lot fewer users of the latest driver code if they
> > have to download, compile and install a entire new kernel. There are
> > plenty of people who will install new drivers, but won't even consider
> > switching from the kernel their distro came with.
>
> 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
> release tarballs to update their existing kernels. So long as those are
> available in a similar form I would expect these users would be
> unaffected.
I have a same impression. I started providing daily snapshot tarballs
because so many people avoid HG when I requested for testing.
A snapshot tarball (of each commit at best) would be a convenient
solution for most of users, I guess.
Takashi
next prev parent reply other threads:[~2008-02-07 15:18 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 [this message]
2008-02-07 16:03 ` Trent Piepho
2008-02-07 19:27 ` Mark Brown
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=s5hzlucyev8.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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