From: James Pickens <jepicken@gmail.com>
To: Git ML <git@vger.kernel.org>, Nicolas Pitre <nico@fluxnic.net>
Subject: [BUG] Git 1.6.6 can't clone tags after filter-branch
Date: Tue, 19 Jan 2010 15:05:21 -0700 [thread overview]
Message-ID: <885649361001191405x7a4ca1a2i153ad952c7d41ad7@mail.gmail.com> (raw)
Hi,
This series of commands:
git init
touch file1
git add file1
git commit -m 1
echo >> file1
touch file2
git add file1 file2
git commit -m 2
git tag -m 'mytag' mytag
git filter-branch --index-filter 'git rm --cached --ignore-unmatch file2' \
--tag-name-filter cat -f -- --all
git clone file://$PWD temp
Results in an error from the clone command:
error: refs/tags/mytag does not point to a valid object!
The clone command exits with zero status, but the new repo doesn't contain
the tag 'mytag'.
Version 1.6.2.5 did not have this problem. It bisects to:
commit 5bdc32d3e50d8335c65e136e6b5234c5dd92a7a9
Author: Nicolas Pitre <nico@fluxnic.net>
Date: Fri Sep 25 23:54:42 2009 -0400
make 'git clone' ask the remote only for objects it cares about
James
reply other threads:[~2010-01-19 22:05 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=885649361001191405x7a4ca1a2i153ad952c7d41ad7@mail.gmail.com \
--to=jepicken@gmail.com \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
/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).