From: karthik nayak <karthik.188@gmail.com>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 2/2] git-C: Add test to check "git -C ''"
Date: Thu, 05 Mar 2015 16:32:12 +0530 [thread overview]
Message-ID: <54F837B4.2060003@gmail.com> (raw)
In-Reply-To: <1425553031-22264-1-git-send-email-karthik.188@gmail.com>
On 03/05/2015 04:27 PM, Karthik Nayak wrote:
> Add a test to check whether "git -C ''" works
> without giving an error. This is achieved by
> adding a commit and checking the log using
> "git -C ''" and comparing the log message with
> the commit message.
>
> Signed-off-by: Karthik Nayak <karthik.188@gmail.com>
> ---
> t/t0056-git-C.sh | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/t/t0056-git-C.sh b/t/t0056-git-C.sh
> index 99c0377..1cefd4a 100755
> --- a/t/t0056-git-C.sh
> +++ b/t/t0056-git-C.sh
> @@ -1,3 +1,4 @@
> +
> #!/bin/sh
>
> test_description='"-C <path>" option and its effects on other path-related options'
> @@ -81,4 +82,13 @@ test_expect_success 'Relative followed by fullpath: "-C ./here -C /there" is equ
> test_cmp expected actual
> '
>
> +test_expect_success 'Should not barf when "git -C "" cmd" is used' '
> + echo 1 > a.txt &&
> + msg="initial a.txt" &&
> + (git add a.txt && git commit -m "$msg") &&
> + echo "$msg" >expected &&
> + git -C "" log --format=%s >actual &&
> + test_cmp expected actual
> +'
> +
> test_done
>
Ignore This, Didnt connect it to the first patch!
next prev parent reply other threads:[~2015-03-05 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 10:57 [PATCH v2 2/2] git-C: Add test to check "git -C ''" Karthik Nayak
2015-03-05 11:02 ` karthik nayak [this message]
2015-03-05 21:39 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2015-03-05 10:56 [PATCH v2 1/2] git: make "git -C '' <cmd>" not to barf Karthik Nayak
2015-03-05 11:03 ` [PATCH v2 2/2] git-C: Add test to check "git -C ''" Karthik Nayak
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=54F837B4.2060003@gmail.com \
--to=karthik.188@gmail.com \
--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.
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).