From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/2] t6200-fmt-merge-msg: Exercise 'merge.log' to configure shortlog length
Date: Sat, 28 Aug 2010 16:05:39 +0530 [thread overview]
Message-ID: <20100828103536.GA12205@kytes> (raw)
In-Reply-To: <20100828020018.GD2004@burratino>
Hi Jonathan,
Jonathan Nieder writes:
> I suspect this test would be easier to understand if split up (yes, I
> know I'm guilty of the same in other tests from this file).
I sort of tried to follow what was done in the rest of the file. If
this style is desired instead, I'll post an alternative series
instead.
> test_expect_success 'setup: clear [merge] configuration' '
> test_might_fail git config --unset-all merge.log &&
> test_might_fail git config --unset-all merge.summary
> '
>
> test_expect_success 'set up FETCH_HEAD' '
> git checkout master &&
> git fetch . left
> '
Okay.
> test_expect_success 'merge.log=3 limits shortlog length' '
> test_might_fail git config --unset merge.log &&
> test_might_fail git config --unset merge.summary &&
Redundant, as you pointed out in another email.
> cat >expected <<-\EOF &&
> Left #3
> ...
> EOF
> git -c merge.log=3 fmt-merge-msg <.git/FETCH_HEAD >msg &&
>
> tail -n 2 msg >actual &&
> test_cmp expected actual
> '
Ok. I don't like the `tail` thing. Why are you doing it instead of
comparing full outputs like the tests in the rest of the file?
> test_expect_success 'shortlog length defaults to 20' '
> [...]
> '
Actually, we can't test this unless we actually create a branch with
20 commits and merge it. I've dropped this- you might like to add it
during the cleanup.
> test_expect_success 'merge.log=5 does not limit shortlog length' '
> [...]
> '
Okay.
> test_expect_success 'merge.log=6 does not limit shortlog length' '
> [...]
> '
I thought this was a bit of an overkill, so I removed it.
> test_expect_success 'merge.log=0 disables shortlog' '
> [...]
> '
Okay.
> test_expect_success 'merge.log=-1 does something sane' '
> [...]
> '
Thanks! I found a bug and fixed it (patch will come in a moment).
> I can clean up the earlier tests afterwards. :)
Okay, sounds good.
-- Ram
next prev parent reply other threads:[~2010-08-28 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 14:14 [PATCH 0/2] Two tests for rr/fmt-merge-msg Ramkumar Ramachandra
2010-08-27 14:14 ` [PATCH 1/2] t6200-fmt-merge-msg: Exercise 'merge.log' to configure shortlog length Ramkumar Ramachandra
2010-08-28 2:00 ` Jonathan Nieder
2010-08-28 2:05 ` Jonathan Nieder
2010-08-28 10:35 ` Ramkumar Ramachandra [this message]
2010-08-28 17:09 ` Jonathan Nieder
2010-08-27 14:14 ` [PATCH 2/2] t6200-fmt-merge-msg: Exercise '--log' " Ramkumar Ramachandra
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=20100828103536.GA12205@kytes \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@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).