All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: HG vs GIT
Date: Thu, 07 Feb 2008 22:14:57 +0100	[thread overview]
Message-ID: <47AB74D1.1070700@keyaccess.nl> (raw)
In-Reply-To: <s5habmdknw0.wl%tiwai@suse.de>

On 07-02-08 12:27, Takashi Iwai 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.
> 
> Maybe we can think reversely.  Keep the kernel git tree as the primary
> development tree and generate the subset as the alsa-kernel package
> from the kernel tree automatically.  In this way, you can avoid also 
> sign-off messes, too.

This sounds good...

> In this scheme, you don't have to stick with stgit.  The normal git
> can handle patches well enough (via occasional rebase), and it's much
> much faster than stgit.  Of course, stgit is still good for small
> number of patches, but it's not true for shared devel trees.

Rene.

  parent reply	other threads:[~2008-02-07 21: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
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 [this message]
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=47AB74D1.1070700@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alsa-devel@alsa-project.org \
    --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.