From: TJ <git@iam.tj>
To: git@vger.kernel.org
Subject: [New Feature] git-submodule-move - Easily move submodules
Date: Sun, 03 Feb 2013 22:36:17 +0000 [thread overview]
Message-ID: <510EE661.8060600@iam.tj> (raw)
I've recently had need to re-arrange more than ten submodules within a project and discovered there is apparently no easy way to do it.
Using some suggestions I found on Stack Overflow I eventually figured out the steps required. Because the steps can be
complex I thought it would be handy to have a tool to automate the functionality.
I have put together a reasonably bullet-proof shell script "git-submodule-move" that does the job pretty well. I've put it through quite a bit of testing and trusted it with my own project and it has
performed well.
I've published to github so others can use and improve it.
https://github.com/iam-TJ/git-submodule-move
next reply other threads:[~2013-02-03 22:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 22:36 TJ [this message]
2013-02-04 20:14 ` [New Feature] git-submodule-move - Easily move submodules Jens Lehmann
-- strict thread matches above, loose matches on Subject: below --
2013-02-09 12:25 [BUG] can't switch branches with submodules Ramkumar Ramachandra
2013-01-07 0:36 Moving (renaming) submodules, recipe/script W. Trevor King
2013-01-07 1:39 ` Jonathan Nieder
2013-01-07 6:59 ` Jens Lehmann
2013-01-07 7:44 ` Junio C Hamano
2013-01-07 8:18 ` Jens Lehmann
2013-01-07 16:08 ` Junio C Hamano
2013-01-07 12:08 ` W. Trevor King
2013-01-08 14:32 ` W. Trevor King
2013-01-08 17:12 ` Jens Lehmann
2013-01-08 17:48 ` W. Trevor King
2013-02-09 12:32 ` [BUG] can't switch branches with submodules W. Trevor King
2013-02-03 23:38 ` Moving (renaming) submodules, recipe/script W. Trevor King
2012-10-22 12:37 Git submodule for a local branch? W. Trevor King
2012-10-23 13:21 ` W. Trevor King
2012-10-23 20:57 ` Jens Lehmann
2012-10-23 22:09 ` W. Trevor King
2013-01-08 15:59 ` Moving (renaming) submodules, recipe/script W. Trevor King
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=510EE661.8060600@iam.tj \
--to=git@iam.tj \
--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.
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).