git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Heiko Voigt <hvoigt@hvoigt.net>
To: "Frawley, Sarah" <sarah.frawley@intel.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Query on git submodules
Date: Tue, 26 May 2015 19:01:25 +0200	[thread overview]
Message-ID: <20150526170125.GC31115@book.hvoigt.net> (raw)
In-Reply-To: <4C328B7D13677A4EAF715D0755A6D7EE25C589BF@irsmsx110.ger.corp.intel.com>

Hi,

On Fri, May 22, 2015 at 01:46:24PM +0000, Frawley, Sarah wrote:
> I am a design automation engineer supporting 200+ designers who use
> git for hardware design.  We also use the submodule feature where we
> can have quite complex hierarchy's with 10+ layers.

What does this 10+ layers mean? Nested submodule repositories 10
recursion steps deep?

> We have experience issues with re-use of design projects was we move
>from one derivative to another due to the complexity of the hierarchy
>along with lack of discipline (using absolute paths in .gitmodule
>files). To enforce more discipline I am currently working on a
>pre-commit hook to check the integrity of .gitmodule files.  I would be
>interested in seeing how other users in the community find submodules
>for large scale projects and if there are any best known methods for
>using them.

I do not have anything to share here since our projects did not have
such problems (not that large scale). It would be interesting to see
what you come up with. Maybe we can add some of that into core git to
support such large scale projects better. So maybe you can share exactly
what problems you have (only absolute paths?) or the pre-commit hooks
you will use.

Cheers Heiko

  reply	other threads:[~2015-05-26 17:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C328B7D13677A4EAF715D0755A6D7EE25C56C89@irsmsx110.ger.corp.intel.com>
2015-05-22 13:46 ` Query on git submodules Frawley, Sarah
2015-05-26 17:01   ` Heiko Voigt [this message]
2015-05-27 13:20     ` FW: " Frawley, Sarah
2015-06-02  9:45       ` Mattias Vannergård
2015-06-02 11:17         ` Heiko Voigt
2015-06-02 11:27           ` Mattias Vannergård
2015-06-02 11:12       ` Heiko Voigt
2015-06-02 14:22         ` Frawley, Sarah

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=20150526170125.GC31115@book.hvoigt.net \
    --to=hvoigt@hvoigt.net \
    --cc=git@vger.kernel.org \
    --cc=sarah.frawley@intel.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).