From: George Papanikolaou <g3orge.app@gmail.com>
To: git@vger.kernel.org
Subject: mv/rm submodules
Date: Mon, 9 Dec 2013 12:59:11 +0200 [thread overview]
Message-ID: <CAByyCQCakKyUqJQDdFrTMf2CUJihRhqSUVCwT21VDN1EOerVWw@mail.gmail.com> (raw)
Hi list,
I was just playing with the new features of 'git mv' in 1.8.5 and
realized that both rm
and mv don't change the .git/config file. Is that on purpuse?
Also after mv you need to run 'submodule update' and I think this should be
documented somewhere.
Thanks..
--
George 'papanikge' Papanikolaou
g3orge.app@gmail.com
next reply other threads:[~2013-12-09 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 10:59 George Papanikolaou [this message]
2013-12-09 17:49 ` mv/rm submodules Jens Lehmann
2014-01-06 19:21 ` [PATCH] mv: better document side effects when moving a submodule Jens Lehmann
2014-01-06 22:40 ` Junio C Hamano
2014-01-07 17:57 ` Jens Lehmann
2014-01-07 21:30 ` [PATCH v2 0/2] better document side effects when [re]moving " Jens Lehmann
2014-01-07 21:31 ` [PATCH v2 1/2] mv: better document side effects when moving " Jens Lehmann
2014-01-07 21:32 ` [PATCH v2 2/2] rm: better document side effects when removing " 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=CAByyCQCakKyUqJQDdFrTMf2CUJihRhqSUVCwT21VDN1EOerVWw@mail.gmail.com \
--to=g3orge.app@gmail.com \
--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).