From: Jeremiah Mahler <jmmahler@gmail.com>
To: caleb@calebthompson.io
Cc: git@vger.kernel.org
Subject: Re: [PATCH v4 1/4] commit test: Use test_config instead of git-config
Date: Thu, 12 Jun 2014 01:41:52 -0700 [thread overview]
Message-ID: <20140612084152.GA6095@hudson.localdomain> (raw)
In-Reply-To: <1402511079-17735-2-git-send-email-caleb@calebthompson.io>
On Wed, Jun 11, 2014 at 01:24:36PM -0500, caleb@calebthompson.io wrote:
> Some of the tests in t/t7507-commit-verbose.sh were still using
> git-config to set configuration. Change them to use the test_config
> helper.
>
> Signed-off-by: Caleb Thompson <caleb@calebthompson.io>
> ---
> t/t7507-commit-verbose.sh | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/t/t7507-commit-verbose.sh b/t/t7507-commit-verbose.sh
> index 2ddf28c..6d778ed 100755
> --- a/t/t7507-commit-verbose.sh
> +++ b/t/t7507-commit-verbose.sh
> @@ -43,7 +43,7 @@ test_expect_success 'verbose diff is stripped out' '
> '
>
> test_expect_success 'verbose diff is stripped out (mnemonicprefix)' '
> - git config diff.mnemonicprefix true &&
> + test_config diff.mnemonicprefix true &&
> git commit --amend -v &&
> check_message message
> '
> @@ -71,7 +71,7 @@ test_expect_success 'diff in message is retained with -v' '
> '
>
> test_expect_success 'submodule log is stripped out too with -v' '
> - git config diff.submodule log &&
> + test_config diff.submodule log &&
> git submodule add ./. sub &&
> git commit -m "sub added" &&
> (
> --
> 2.0.0
>
It is probably something dumb on my part but for some reason I cannot
apply this patch using 'git am'. After I save the patch to a Maildir
from Mutt and run git am...
jeri@hudson:~/git$ ./git-am ct1.patch
Applying: commit test: Use test_config instead of git-config
fatal: corrupt patch at line 15
Patch failed at 0001 commit test: Use test_config instead of git-config
The copy of the patch that failed is found in:
/home/jeri/git/.git/rebase-apply/patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
jeri@hudson:~/git$
The second patch in the series applies fine. And I have applied other
patches this way without issue. Can anyone confirm this problem?
--
Jeremiah Mahler
jmmahler@gmail.com
http://github.com/jmahler
next prev parent reply other threads:[~2014-06-12 8:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 18:24 [PATCH v4 0/4] commit: support commit.verbose and --no-verbose caleb
2014-06-11 18:24 ` [PATCH v4 1/4] commit test: Use test_config instead of git-config caleb
2014-06-12 8:41 ` Jeremiah Mahler [this message]
2014-06-12 13:51 ` Caleb Thompson
2014-06-12 18:04 ` Jeremiah Mahler
2014-06-12 18:08 ` Jeremiah Mahler
2014-06-12 18:23 ` Caleb Thompson
2014-06-12 18:46 ` Jeremiah Mahler
2014-06-12 19:23 ` Caleb Thompson
2014-06-11 18:24 ` [PATCH v4 2/4] commit test: Use write_script caleb
2014-06-11 18:24 ` [PATCH v4 3/4] commit test: test_set_editor in each test caleb
2014-06-11 18:24 ` [PATCH v4 4/4] commit: support commit.verbose and --no-verbose caleb
2014-06-11 20:41 ` René Scharfe
2014-06-11 21:26 ` Caleb Thompson
2014-06-12 14:36 ` Caleb Thompson
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=20140612084152.GA6095@hudson.localdomain \
--to=jmmahler@gmail.com \
--cc=caleb@calebthompson.io \
--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).