From: Yaroslav Halchenko <yoh@onerussian.com>
To: git@vger.kernel.org
Cc: Stefan Beller <sbeller@google.com>
Subject: in case you want a use-case with lots of submodules
Date: Mon, 19 Jun 2017 11:59:24 -0400 [thread overview]
Message-ID: <20170619155924.7ra2vwvaelr2yj2v@hopa.kiewit.dartmouth.edu> (raw)
Hi All,
On a recent trip I've listened to the git minutes podcast episode and
got excited to hear Stefan Beller (CCed just in case) describing
ongoing work on submodules mechanism. I got excited, since e.g.
performance improvements would be of great benefit to us too.
In our project, http://datalad.org, git submodules is the basic
mechanism to bring multiple "datasets" (mix of git and git-annex'ed
repositories) under the same roof so we could non-ambiguously
version them all at any level.
http://datasets.datalad.org ATM provides quite a sizeable (ATM 370
repositories, up to 4 levels deep) hierarchy of git/git-annex
repositories all tied together via git submodules mechanism. And as the
collection grows, interactions with it become slower, so additional
options (such as --ignore-submodules=dirty to status) become our
friends.
So I thought to share this as a use-case happen you need more
motivation or just a real-case test-bed for your work. And thank
you again for making Git even Greater.
P.S. Please CCme in your replies (if any), I am not on the list
With best regards,
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
next reply other threads:[~2017-06-19 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 15:59 Yaroslav Halchenko [this message]
2017-06-19 19:30 ` in case you want a use-case with lots of submodules Stefan Beller
2017-06-19 20:20 ` Yaroslav Halchenko
2017-06-20 5:43 ` Stefan Beller
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170619155924.7ra2vwvaelr2yj2v@hopa.kiewit.dartmouth.edu \
--to=yoh@onerussian.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).