From: Alexander Inyukhin <shurick@sectorb.msk.ru>
To: git@vger.kernel.org
Subject: git-subtree pull issue
Date: Sat, 17 Sep 2016 01:39:26 +0300 [thread overview]
Message-ID: <20160916223926.irf7q4ugjnwwmado@shurick.grid.su> (raw)
When git-subtree is pulling data using the tag reference,
it writes the tag's sha1 into a metadata.
It could be a problem next time, since this commit object
is not a part of main tree, and could be lost.
Steps to reproduce:
# add some stuff to a existing tree
# history will refer to v0.1 tag object instead of v0.1^{commit}
git subtree add --squash -P dir/ repo v0.1
# prune all dangling objects including external v0.1 tag
git gc --aggressive --prune=all
# this will fail
git subtree pull --squash -P dir/ repo v0.2
reply other threads:[~2016-09-16 22:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160916223926.irf7q4ugjnwwmado@shurick.grid.su \
--to=shurick@sectorb.msk.ru \
--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