From: Semen Vadishev <semen.vadishev@tmatesoft•com>
To: git@vger•kernel.org
Subject: Delete gitlink entry but keep .gitmodules file unmodified
Date: Wed, 18 Apr 2012 17:19:25 +0400 [thread overview]
Message-ID: <4F8EBF5D.5070301@tmatesoft.com> (raw)
Suppose one has a properly initialized submodule in a tree like this:
$ git ls-tree HEAD
100644 blob d208248ba4ab1d1791dc27f451dcaedb87dc19e1 .gitmodules
160000 commit ec633ea81e3cf64c3735ef4acd5ff9a490ed54eb ext
100644 blob 597d6924118c00054efd526d9e48f68198f7da12 file.txt
$ git show HEAD:.gitmodules
[submodule "ext"]
path = ext
url = $URL
Then one pulls a modification that replaces 'ext' gitlink by some blob
or tree entry, but keeps '.gitmodules' the same:
$ git ls-tree HEAD
100644 blob d208248ba4ab1d1791dc27f451dcaedb87dc19e1 .gitmodules
040000 tree 82e3a754b6a0fcb238b03c0e47d05219fbf9cf89 ext
100644 blob 597d6924118c00054efd526d9e48f68198f7da12 file.txt
Are there any possible downsides of such modification we should be aware of?
Thanks,
--
Semen Vadishev,
TMate Software,
http://subgit.com/ - git+svn on the server side!
next reply other threads:[~2012-04-18 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 13:19 Semen Vadishev [this message]
2012-04-18 13:42 ` Delete gitlink entry but keep .gitmodules file unmodified Jens Lehmann
2012-04-18 14:34 ` Semen Vadishev
2012-04-19 9:10 ` 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=4F8EBF5D.5070301@tmatesoft.com \
--to=semen.vadishev@tmatesoft$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/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