From: Junio C Hamano <gitster@pobox.com>
To: Kevin Ballard <kevin@sb.org>
Cc: git@vger.kernel.org
Subject: Re* [PATCH] Add test for filter-branch on a subdirectory that's been added and deleted and re-added
Date: Sat, 08 Mar 2008 12:08:58 -0800 [thread overview]
Message-ID: <7vmyp9t1ut.fsf_-_@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <91DF7A2E-540B-4AD6-91B2-BDB0B04EFC71@sb.org> (Kevin Ballard's message of "Sat, 8 Mar 2008 13:45:17 -0500")
Kevin Ballard <kevin@sb.org> writes:
> On Mar 8, 2008, at 1:41 PM, Junio C Hamano wrote:
>
>> Such a test is a very good incentive to the people involved in the
>> failing
>> part of the system to fix, and is greatly appreciated. However,
>>
>> * please mark "currently-failing" test with "test_expect_failure";
>
> Ahh, didn't know about that. In retrospect I should have been able to
> guess, though.
>
>> * please hint (after --- lines) if you will shortly be following up
>> with
>> a fix patch yourself, or if you are only reporting a bug.
>
> Ah. Yeah, I'm only reporting a bug. I don't know anything about how
> this stuff works, and the bug doesn't bite me, it bit someone else
> instead, I just thought it deserved to be documented somewhere as a
> failure.
>
>> I can fix-up and forge your Sign-off.
>
> That would be great, thanks.
Heh, your test is broken. You are not re-adding foo.
Here is a fix.
---
git-filter-branch.sh | 11 ++++++++++-
t/t7003-filter-branch.sh | 5 ++++-
2 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/git-filter-branch.sh b/git-filter-branch.sh
index 49e13f0..8382212 100755
--- a/git-filter-branch.sh
+++ b/git-filter-branch.sh
@@ -252,7 +252,16 @@ while read commit parents; do
git read-tree -i -m $commit
;;
*)
- git read-tree -i -m $commit:"$filter_subdir"
+ # The commit may not have the subdirectory at all
+ err=$(git read-tree -i -m $commit:"$filter_subdir" 2>&1) || {
+ if ! git rev-parse $commit:"$filter_subdir" 2>&1
+ then
+ rm -f "$GIT_INDEX_FILE"
+ else
+ echo >&2 "$err"
+ false
+ fi
+ }
esac || die "Could not initialize the index"
GIT_COMMIT=$commit
diff --git a/t/t7003-filter-branch.sh b/t/t7003-filter-branch.sh
index 2ea8e3b..8f92fef 100755
--- a/t/t7003-filter-branch.sh
+++ b/t/t7003-filter-branch.sh
@@ -188,8 +188,11 @@ test_expect_failure 'Subdirectory filter on folder with non-contiguous history'
git commit -m "Removing foo" &&
mkdir foo &&
touch foo/bar &&
+ git add foo &&
git commit -m "Re-adding foo" &&
- git filter-branch --subdirectory-filter foo
+
+ git filter-branch --subdirectory-filter foo &&
+ test $(git rev-list master | wc -l) = 3
'
test_done
next prev parent reply other threads:[~2008-03-08 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 11:50 [PATCH] Add test for filter-branch on a subdirectory that's been added and deleted and re-added Kevin Ballard
2008-03-08 11:52 ` Kevin Ballard
2008-03-08 18:41 ` Junio C Hamano
2008-03-08 18:45 ` Kevin Ballard
2008-03-08 20:08 ` Junio C Hamano [this message]
2008-03-08 20:25 ` Junio C Hamano
2008-03-08 20:39 ` Kevin Ballard
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=7vmyp9t1ut.fsf_-_@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kevin@sb.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).