From: Junio C Hamano <gitster@pobox.com>
To: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH 1/4] rebase -i: demonstrate obscure loose object cache bug
Date: Thu, 14 Mar 2019 10:12:08 +0900 [thread overview]
Message-ID: <xmqqimwmcl93.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <b3fcd377652103584b6f307c6ee209980b44529f.1552472189.git.gitgitgadget@gmail.com> (Johannes Schindelin via GitGitGadget's message of "Wed, 13 Mar 2019 03:16:31 -0700 (PDT)")
"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
writes:
> +test_expect_failure SHA1 'loose object cache vs re-reading todo list' '
> + GIT_REBASE_TODO=.git/rebase-merge/git-rebase-todo &&
> + export GIT_REBASE_TODO &&
> + write_script append-todo.sh <<-\EOS &&
> + # For values 5 and 6, this yields SHA-1s with the same first two digits
> + echo "pick $(git rev-parse --short \
> + $(printf "%s\\n" \
> + "tree $EMPTY_TREE" \
> + "author A U Thor <author@example.org> $1 +0000" \
> + "committer A U Thor <author@example.org> $1 +0000" \
> + "" \
> + "$1" |
> + git hash-object -t commit -w --stdin))" >>$GIT_REBASE_TODO
In the generated append-todo.sh, as the <<EOS above is quoted, we
will see ">>$GIT_REBASE_TODO" literally (not the actual pathname
that begins with .git, but a reference to the variable). test-lint
may or may not catch it, but redirecting into variable reference
would trigger a(n arguably misguided) warning when run with some
versions of bash. Quoting
echo ... >>"$GIT_REBASE_TODO"
would work it around, of course.
> + shift
> + test -z "$*" ||
> + echo "exec $0 $*" >>$GIT_REBASE_TODO
Likewise.
> + EOS
> +
> + git rebase HEAD -x "./append-todo.sh 5 6"
> +'
> +
> test_done
next prev parent reply other threads:[~2019-03-14 1:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 10:16 [PATCH 0/4] get_oid: cope with a possibly stale loose object cache Johannes Schindelin via GitGitGadget
2019-03-13 10:16 ` [PATCH 1/4] rebase -i: demonstrate obscure loose object cache bug Johannes Schindelin via GitGitGadget
2019-03-13 16:11 ` Ævar Arnfjörð Bjarmason
2019-03-13 16:35 ` Jeff King
2019-03-13 16:53 ` Jeff King
2019-03-13 22:40 ` Johannes Schindelin
2019-03-14 0:07 ` Jeff King
2019-03-13 22:27 ` Johannes Schindelin
2019-03-14 0:05 ` Jeff King
2019-03-14 6:40 ` Johannes Sixt
2019-03-14 13:06 ` Johannes Schindelin
2019-03-14 1:12 ` Junio C Hamano [this message]
2019-03-14 12:44 ` Johannes Schindelin
2019-03-13 10:16 ` [PATCH 2/4] sequencer: improve error message when an OID could not be parsed Johannes Schindelin via GitGitGadget
2019-03-14 1:14 ` Junio C Hamano
2019-03-13 10:16 ` [PATCH 3/4] sequencer: move stale comment into correct location Johannes Schindelin via GitGitGadget
2019-03-13 10:16 ` [PATCH 4/4] get_oid(): when an object was not found, try harder Johannes Schindelin via GitGitGadget
2019-03-14 1:29 ` Junio C Hamano
2019-03-14 2:22 ` Jeff King
2019-03-14 2:40 ` Jeff King
2019-03-14 4:05 ` Junio C Hamano
2019-03-14 18:55 ` Jeff King
2019-03-14 3:49 ` Junio C Hamano
2019-03-14 13:17 ` Johannes Schindelin
2019-03-14 18:57 ` Jeff King
2019-03-14 19:55 ` Johannes Schindelin
2019-03-13 15:33 ` [PATCH 0/4] get_oid: cope with a possibly stale loose object cache Jeff King
2019-03-14 15:33 ` [PATCH v2 0/4] get_short_oid: " Johannes Schindelin via GitGitGadget
2019-03-14 15:33 ` [PATCH v2 1/4] rebase -i: demonstrate obscure loose object cache bug Johannes Schindelin via GitGitGadget
2019-03-14 15:33 ` [PATCH v2 2/4] sequencer: improve error message when an OID could not be parsed Johannes Schindelin via GitGitGadget
2019-03-14 15:33 ` [PATCH v2 3/4] sequencer: move stale comment into correct location Johannes Schindelin via GitGitGadget
2019-03-14 15:33 ` [PATCH v2 4/4] get_oid(): when an object was not found, try harder Johannes Schindelin via GitGitGadget
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqimwmcl93.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=johannes.schindelin@gmx.de \
--cc=peff@peff.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).