From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Andrew Paprocki <andrew@ishiboo.com>
Subject: Re: HG vs GIT
Date: Thu, 07 Feb 2008 16:13:07 +0100 [thread overview]
Message-ID: <s5h1w7oztoc.wl%tiwai@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0802071314430.8113@tm8103.perex-int.cz>
At Thu, 7 Feb 2008 13:19:49 +0100 (CET),
Jaroslav Kysela wrote:
>
> On Thu, 7 Feb 2008, Takashi Iwai wrote:
>
> > At Thu, 7 Feb 2008 06:45:10 -0500,
> > Andrew Paprocki wrote:
> > >
> > > On Feb 7, 2008 6:27 AM, Takashi Iwai <tiwai@suse.de> wrote:
> > > > BTW, one big annoying thing is that developers have no complete kernel
> > > > tree to access, and thus the patches that touch outside the ALSA
> > > > subdirectory cannot be merged easily. People often send patches
> > > > fixing together with OSS, etc, and I had to skip them. So, frankly,
> > > > I'd love to have an access to the whole kernel tree. But, OTOH, this
> > > > would make harder for other naive guys to give it a try because they
> > > > need to download the big linux kernel tree git.
> > >
> > > I was just wondering about this the other day.. I don't think using
> > > kernel git trees would put anyone off. Anyone working on a sound card
> > > driver would most likely already be familiar with using git w/ the
> > > upstream kernel anyway.
> >
> > 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!"
>
> I have an idea to create a web interface generating the alsa-kernel like
> tree on the fly (with some caching, of course). It might also apply for
> all ALSA packages. It would be quite nice to point users to very recent
> code and not to wait for daily tarballs.
This would be helpful indeed.
Takashi
next prev parent reply other threads:[~2008-02-07 15:13 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 [this message]
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
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=s5h1w7oztoc.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=andrew@ishiboo.com \
--cc=perex@perex.cz \
/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