From: Petr Baudis <pasky@suse•cz>
To: Rob Sanheim <rsanheim@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: Q: how to remove or move submodules?
Date: Wed, 23 Jul 2008 01:22:40 +0200 [thread overview]
Message-ID: <20080722232240.GL32184@machine.or.cz> (raw)
In-Reply-To: <fc113d400807122338o637cc159n5e19fea5a15dc866@mail.gmail.com>
Hi,
On Sun, Jul 13, 2008 at 02:38:51AM -0400, Rob Sanheim wrote:
> I don't see any info on what the 'right' way is to delete or move
> submodules around in any of the docs. Normally I end up just hacking
> my way through it and hand modifying the .gitmodules file, but this
> seems wrong. Is there a recommended way?
currently, you have to hand-modify the .gitmodules file, then remove
the directory from the working tree and then from the index. In part
inspired by your question, I have submitted patches to add git mv and
git rm support for submodules some time ago, but they probably won't
make it to 1.6.0.
Petr "Pasky" Baudis
prev parent reply other threads:[~2008-07-22 23:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 6:38 Q: how to remove or move submodules? Rob Sanheim
2008-07-22 23:22 ` Petr Baudis [this message]
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=20080722232240.GL32184@machine.or.cz \
--to=pasky@suse$(echo .)cz \
--cc=git@vger$(echo .)kernel.org \
--cc=rsanheim@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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