From: Gregor Jasny <gjasny@googlemail.com>
To: git@vger.kernel.org
Subject: Re: Git subtree stumbles over annotated tags
Date: Thu, 17 Mar 2016 13:41:00 +0100 [thread overview]
Message-ID: <56EAA5DC.1040801@googlemail.com> (raw)
In-Reply-To: <56E19809.5040305@googlemail.com>
Hello,
On 10/03/16 16:51, Gregor Jasny wrote:
> today I discovered that it's a bad idea to "git subtree pull" from an
> annotated tag. This issue got discussed in those two threads:
>
> http://comments.gmane.org/gmane.comp.version-control.git/247503
> http://comments.gmane.org/gmane.comp.version-control.git/248395
>
> I was under the impression that it is fixed in recent versions of git
> but my homebrew 2.7.0 still behaves badly. If I run the attached script
> to reproduce the issue I get the following error message:
For the record: this bug was already fixed in November:
https://github.com/git/git/commit/5d65fe312e22594b7fec7349945fb0072987716b#diff-59f70cbe935ec223e3df413b94cab740
Would it make sense to cherry-pick it into 2.7.x?
Thanks,
Gregor
next prev parent reply other threads:[~2016-03-17 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 15:51 Git subtree stumbles over annotated tags Gregor Jasny
2016-03-17 12:41 ` Gregor Jasny [this message]
2016-05-21 23:02 ` David A. Greene
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=56EAA5DC.1040801@googlemail.com \
--to=gjasny@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.