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>,
	git-devel@vger.kernel.org
Subject: GIT submodules
Date: Thu, 07 Feb 2008 22:10:47 +0100	[thread overview]
Message-ID: <47AB73D7.7060707@keyaccess.nl> (raw)
In-Reply-To: <s5h7ihhknez.wl%tiwai@suse.de>

On 07-02-08 12:37, Takashi Iwai wrote:

>> I believe the git submodule stuff would also nicely allow all of ALSA to be 
>> one giant repo basically, with kernel, lib, ..., as submodules.
> 
> Just out of curiosity, what could be a merit of submodules in the case
> of ALSA?

Given that they're used for larger projects, I can't say I've used them but 
I read about them when Linus mentioned them in the context of KDE maybe 
switching:

http://lwn.net/Articles/246381/

Basically, submodules are the  actual git repositories with one organizing 
superproject. This seems to be a fairly nice description of the submodule 
support:

http://www.ishlif.org/blog/linux/git-submodules/

What they provide is stitching the parts together nicely into one coherent 
release. In this case, you'd have alsa-driver, alsa-lib, alsa-utils and so 
on repos, and an "alsa-project" superproject tying them together, where you 
could do checkouts of a complete coherent release off all the modules for 
example.

As said, I haven't actually used them, so I've added the git list (*) to see 
if anyone has something to add, correct or explain (please do!). Submodules 
seem to be intended exactly for the kind of setup that ALSA is using with 
the many semi-independent parts...

(*) git-devel: alsa-devel is moderated for non-subscribers but you'll be 
whitelisted after landing in the queue once if you're not a subscriber

Rene.

  reply	other threads:[~2008-02-07 21:09 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 15:02 HG branches Takashi Iwai
2008-02-06 14:04 ` Jaroslav Kysela
2008-02-06 14:06   ` Jaroslav Kysela
2008-02-06 16:13     ` Takashi Iwai
2008-02-06 20:06     ` Rene Herman
2008-02-07 11:37       ` Takashi Iwai
2008-02-07 21:10         ` Rene Herman [this message]
2008-02-07 21:24         ` GIT submodules Rene Herman
2008-02-07  1:59     ` HG branches Seth Forshee
2008-02-07  8:18       ` Jaroslav Kysela
2008-02-07 11:30       ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2008-04-28 19:50 git submodules Victor Bogado da Silva Lins
2008-04-28 21:01 ` Miklos Vajna
2008-07-28 16:20 Pierre Habouzit
2008-07-28 16:23 ` Pierre Habouzit
2008-07-28 20:23 ` Nigel Magnay
2008-07-28 20:55   ` Pierre Habouzit
2008-07-28 20:59     ` Pierre Habouzit
2008-07-28 21:40       ` Avery Pennarun
2008-07-28 22:03         ` Pierre Habouzit
2008-07-28 22:26           ` Jakub Narebski
2008-07-28 22:41             ` Junio C Hamano
2008-08-17 20:13               ` Pierre Habouzit
2008-08-17 22:54                 ` Avery Pennarun
2008-08-17 23:08                 ` Junio C Hamano
2008-08-18  0:46                   ` Pierre Habouzit
2008-07-28 22:32           ` Avery Pennarun
2008-07-28 23:12             ` Pierre Habouzit
2008-07-29  5:51         ` Benjamin Collins
2008-07-29  6:04           ` Shawn O. Pearce
2008-07-29  8:18             ` Nigel Magnay
2008-07-29  8:45               ` Pierre Habouzit
2008-07-29  8:21           ` Pierre Habouzit
2008-07-29  8:37             ` Pierre Habouzit
2008-07-29  8:51               ` Petr Baudis
2008-07-29 12:15                 ` Johannes Schindelin
2008-07-29 13:07                   ` Pierre Habouzit
2008-07-29 13:15                     ` Johannes Schindelin
2008-07-29 13:19                       ` Pierre Habouzit
2008-07-29 13:31                       ` Nigel Magnay
2008-07-29 14:49                         ` Pierre Habouzit
2008-07-29 14:53                         ` Junio C Hamano
2009-10-17 17:15 Steven Noonan
2009-10-17 17:27 ` Jakub Narebski
2009-10-17 22:30   ` Nanako Shiraishi
2009-10-21 19:38 ` Avery Pennarun

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=47AB73D7.7060707@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alsa-devel@alsa-project.org \
    --cc=git-devel@vger.kernel.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.