git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Hord <hordp@cisco.com>
To: Fredrik Gustafsson <iveqy@iveqy.com>
Cc: git@vger.kernel.org, hvoigt@hvoigt.net, jens.lehmann@web.de
Subject: Re: [GSoC 11 submodule] Status update
Date: Mon, 27 Jun 2011 20:29:18 -0400	[thread overview]
Message-ID: <4E09205E.2080904@cisco.com> (raw)
In-Reply-To: <20110627193444.GA26778@paksenarrion.iveqy.com>

Hi Fredrik and git-submodule folks,

On 06/27/2011 03:34 PM, Fredrik Gustafsson wrote:
> My fourth task (and the main task of this summer) will start on June 27 and
> will be to move a submodules .git-dir into the super-projects .git-dir.
> Design of this is already done and approved by my mentors.

This frightens me a bit, so I read the wiki link about it.  Thanks for
explaining where I can find this information.

But I'm still confused.

If I understand right, the submodule/.git dirs will be moved into the
top-level at .git/submodule/.git.  The benefit is supposed to be that
this will free up contention on the non-empty submodule directory when
the super-project switches branches.

In the simple case, git warns "unable to rmdir sub: Directory not
empty".  But I can think of other conflicts as well.

My question is, how does this proposed change help the situation?

Phil

  reply	other threads:[~2011-06-28  0:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 19:34 [GSoC 11 submodule] Status update Fredrik Gustafsson
2011-06-28  0:29 ` Phil Hord [this message]
2011-06-28 18:43   ` Heiko Voigt
2011-06-29 21:27     ` Phil Hord
2011-06-29 21:58       ` Junio C Hamano
2011-06-30 17:54         ` Phil Hord

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=4E09205E.2080904@cisco.com \
    --to=hordp@cisco.com \
    --cc=git@vger.kernel.org \
    --cc=hvoigt@hvoigt.net \
    --cc=iveqy@iveqy.com \
    --cc=jens.lehmann@web.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 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 NNTP newsgroup(s).