From: Junio C Hamano <gitster@pobox.com>
To: Will Palmer <wmpalmer@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCHv2 1/2] add basic tests for merge-tree
Date: Tue, 13 Jul 2010 16:31:28 -0700 [thread overview]
Message-ID: <7vaapv0xin.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1278854215-9022-2-git-send-email-wmpalmer@gmail.com> (Will Palmer's message of "Sun\, 11 Jul 2010 14\:16\:54 +0100")
Will Palmer <wmpalmer@gmail.com> writes:
> merge-tree had no test cases, so here we add some very basic tests for
> it, including some known-breakages.
>
> Signed-off-by: Will Palmer <wmpalmer@gmail.com>
> ---
> t/t4300-merge-tree.sh | 277 +++++++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 277 insertions(+), 0 deletions(-)
> create mode 100755 t/t4300-merge-tree.sh
This does not sound like part of "the diff commands", unlike apply/diff/log.
Perhaps somewhere in t3xxx "other basic commands" series?
> diff --git a/t/t4300-merge-tree.sh b/t/t4300-merge-tree.sh
> new file mode 100755
> index 0000000..b2ae3a1
> --- /dev/null
> +++ b/t/t4300-merge-tree.sh
> @@ -0,0 +1,277 @@
> ...
> +test_expect_'file add A, !B' '
> + cat >expected <<EXPECTED
> +added in remote
> + their 100644 43d5a8ed6ef6c00ff775008633f95787d088285d ONE
> +@@ -0,0 +1 @@
> ++AAA
> +EXPECTED
Since you do not use any variable substitution in the here text, please
make that clear by quoting EXPECTED like this:
cat >expected <<\EXPECTED
... your here text goes here ...
EXPECTED
to help the readers, who otherwise have to scan the here text to find if
there is any interesting substitution going on.
> + git reset --hard initial
> + test_commit "add-a-not-b" "ONE" "AAA"
Please fix missing && cascades.
Thanks.
next prev parent reply other threads:[~2010-07-13 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 13:16 [PATCHv2 0/2] merge-tree: fix (merge-base a b) b a Will Palmer
2010-07-11 13:16 ` [PATCHv2 1/2] add basic tests for merge-tree Will Palmer
2010-07-13 23:31 ` Junio C Hamano [this message]
2010-07-14 7:01 ` Will Palmer
2010-07-14 16:26 ` Junio C Hamano
2010-07-11 13:16 ` [PATCHv2 2/2] fix merge-tree where two branches share no changes Will Palmer
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=7vaapv0xin.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=wmpalmer@gmail.com \
/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).