From: Joey Hess <joeyh@joeyh.name>
To: git@vger.kernel.org
Cc: Joey Hess <joeyh@joeyh.name>
Subject: [PATCH 4/4] use smudge-to-file in git checkout etc
Date: Thu, 16 Jun 2016 16:32:59 -0400 [thread overview]
Message-ID: <20160616203259.5886-5-joeyh@joeyh.name> (raw)
In-Reply-To: <20160616203259.5886-1-joeyh@joeyh.name>
This makes git checkout, git reset, etc use smudge-to-file.
Includes test cases.
(There's a call to convert_to_working_tree in merge-recursive.c
that could also be made to use smudge-to-file as well.)
Signed-off-by: Joey Hess <joeyh@joeyh.name>
---
entry.c | 34 +++++++++++++++++++++++++++-------
t/t0021-conversion.sh | 44 ++++++++++++++++++++++++++++++++++++--------
2 files changed, 63 insertions(+), 15 deletions(-)
diff --git a/entry.c b/entry.c
index 519e042..6a23159 100644
--- a/entry.c
+++ b/entry.c
@@ -175,8 +175,12 @@ static int write_entry(struct cache_entry *ce,
/*
* Convert from git internal format to working tree format
+ * unless the smudge-to-file filter can write to the
+ * file directly.
*/
+ int smudge_to_file = can_smudge_to_file(ce->name);
if (ce_mode_s_ifmt == S_IFREG &&
+ ! smudge_to_file &&
convert_to_working_tree(ce->name, new, size, &buf)) {
free(new);
new = strbuf_detach(&buf, &newsize);
@@ -189,13 +193,29 @@ static int write_entry(struct cache_entry *ce,
return error_errno("unable to create file %s", path);
}
- wrote = write_in_full(fd, new, size);
- if (!to_tempfile)
- fstat_done = fstat_output(fd, state, &st);
- close(fd);
- free(new);
- if (wrote != size)
- return error("unable to write file %s", path);
+ if (! can_smudge_to_file(ce->name)) {
+ wrote = write_in_full(fd, new, size);
+ if (!to_tempfile)
+ fstat_done = fstat_output(fd, state, &st);
+ close(fd);
+ free(new);
+ if (wrote != size)
+ return error("unable to write file %s", path);
+ }
+ else {
+ close(fd);
+ convert_to_working_tree_filter_to_file(ce->name, path, new, size);
+ free(new);
+ if (!to_tempfile) {
+ /* Re-open the file to stat it; the
+ * smudge-to-file filter may have replaced
+ * the file. */
+ fd = open(path, O_RDONLY);
+ if (fd < 0) {
+ return error_errno("unable to create file %s", path);
+ }
+ }
+ }
break;
case S_IFGITLINK:
if (to_tempfile)
diff --git a/t/t0021-conversion.sh b/t/t0021-conversion.sh
index 1043ea5..b0e2e5e 100755
--- a/t/t0021-conversion.sh
+++ b/t/t0021-conversion.sh
@@ -14,12 +14,20 @@ chmod +x rot13.sh
cat <<EOF >rot13-from-file.sh
#!$SHELL_PATH
-fsfile="\$1"
+srcfile="\$1"
touch rot13-from-file.ran
-cat "\$fsfile" | ./rot13.sh
+cat "\$srcfile" | ./rot13.sh
EOF
chmod +x rot13-from-file.sh
+cat <<EOF >rot13-to-file.sh
+#!$SHELL_PATH
+destfile="\$1"
+touch rot13-to-file.ran
+./rot13.sh > "\$destfile"
+EOF
+chmod +x rot13-to-file.sh
+
test_expect_success setup '
git config filter.rot13.smudge ./rot13.sh &&
git config filter.rot13.clean ./rot13.sh &&
@@ -291,17 +299,37 @@ test_expect_success 'clean-from-file filter is used when adding a file' '
cmp test.t fstest.t
'
+test_expect_success 'smudge-to-file filter is used when checking out a file' '
+ test_config filter.rot13.smudge-to-file "./rot13-to-file.sh %p" &&
+
+ rm -f fstest.t &&
+ git checkout -- fstest.t &&
+ cmp test.t fstest.t &&
+
+ test -e rot13-to-file.ran &&
+ rm -f rot13-to-file.ran
+'
+
test_expect_success 'clean-from-file filter is not used when clean filter is not configured' '
- test_config filter.no.smudge ./rot13.sh &&
- test_config filter.no.clean-from-file "./rot13-from-file.sh %p" &&
+ test_config filter.noclean.smudge ./rot13.sh &&
+ test_config filter.noclean.clean-from-file "./rot13-from-file.sh %p" &&
- echo "*.no filter=no" >.gitattributes &&
+ echo "*.no filter=noclean" >.gitattributes &&
cat test.t >test.no &&
git add test.no &&
- test ! -e rot13-from-file.ran &&
- git cat-file blob :test.no >actual &&
- cmp test.t actual
+ test ! -e rot13-from-file.ran
+'
+
+test_expect_success 'smudge-to-file filter is not used when smudge filter is not configured' '
+ test_config filter.nosmudge.clean ./rot13.sh &&
+ test_config filter.nosmudge.smudge-to-file "./rot13-to-file.sh %p" &&
+
+ echo "*.no filter=nosmudge" >.gitattributes &&
+
+ rm -f fstest.t &&
+ git checkout -- fstest.t &&
+ test ! -e rot13-to-file.ran
'
test_done
--
2.9.0.4.g2856e74.dirty
next prev parent reply other threads:[~2016-06-16 20:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 20:32 [PATCH 0/4] extend smudge/clean filters with direct file access Joey Hess
2016-06-16 20:32 ` [PATCH 1/4] clarify %f documentation Joey Hess
2016-06-16 21:33 ` Junio C Hamano
2016-06-17 2:48 ` Joey Hess
2016-06-17 3:25 ` Junio C Hamano
2016-06-17 12:32 ` Joey Hess
2016-06-17 15:57 ` Junio C Hamano
2016-06-16 20:32 ` [PATCH 2/4] add smudge-to-file and clean-from-file filter configuration Joey Hess
2016-06-16 21:57 ` Junio C Hamano
2016-06-17 13:13 ` Joey Hess
2016-06-17 18:26 ` Junio C Hamano
2016-06-17 6:05 ` Eric Sunshine
2016-06-17 9:36 ` Michael J Gruber
2016-06-17 12:47 ` Joey Hess
2016-06-17 16:09 ` Junio C Hamano
2016-06-17 17:29 ` Junio C Hamano
2016-06-17 17:37 ` Joey Hess
2016-06-17 18:06 ` Joey Hess
2016-06-17 18:24 ` Junio C Hamano
2016-06-16 20:32 ` [PATCH 3/4] use clean-from-file in git add Joey Hess
2016-06-16 20:32 ` Joey Hess [this message]
2016-06-16 20:55 ` [PATCH 4/4] use smudge-to-file in git checkout etc Joey Hess
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=20160616203259.5886-5-joeyh@joeyh.name \
--to=joeyh@joeyh.name \
--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;
as well as URLs for NNTP newsgroup(s).