git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Packham <judge.packham@gmail.com>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: state of the art with moving submodules
Date: Tue, 26 Feb 2013 21:09:54 +1300	[thread overview]
Message-ID: <512C6DD2.4000208@gmail.com> (raw)
In-Reply-To: <bcaec55555fe91182f04d698b37f@google.com>

Hi Jens,

(sorry for the dup. gmail insists on sending html)

I know I saw a few threads regarding support for moving submodules but I
lost track of the discussion.

At $dayjob we were discussing a potential re-org of our super-projects
to introduce a bit of hierarchy to the submodules (at the moment it's
fairly flat). One downside of this is the potential loss of locally
committed work. There is also a cost in terms of additional fetching but
we think that will be OK (fetches from local servers with smallish repos).

I was just wondering where things were at with git detecting submodule
moving/renaming? Will our developers be able to keep any local commits
when they happen to pull in the super-project commit that moves a commit.

I think some people with older clones will suffer without the newer
.git/modules layout but those can be manually fixed prior to the re-org.

FYI our current stock workstation install uses git version 1.7.9.5 but
I'm recommending we update to 1.8.x before this re-org to pick up some
of the recent submodule improvements.

Thanks
Chris

       reply	other threads:[~2013-02-26  8:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bcaec55555fe91182f04d698b37f@google.com>
2013-02-26  8:09 ` Chris Packham [this message]
2013-02-26 18:25   ` state of the art with moving submodules Jens Lehmann

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=512C6DD2.4000208@gmail.com \
    --to=judge.packham@gmail.com \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    /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).