Git development
 help / color / mirror / Atom feed
From: Jharrod LaFon <jlafon@eyesopen.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] Git segmentation faults if submodule path is empty.
Date: Mon, 19 Aug 2013 17:26:39 -0700	[thread overview]
Message-ID: <D9B32897-9ABC-4F98-BE8B-CCC105FCAD9E@eyesopen.com> (raw)
In-Reply-To: <xmqq1u5p8kqc.fsf@gitster.dls.corp.google.com>

It looks great to me.

Thanks,

--
Jharrod LaFon
OpenEye Scientific Software

On Aug 19, 2013, at 2:54 PM, Junio C Hamano <gitster@pobox.com> wrote:

> Jharrod LaFon <jlafon@eyesopen.com> writes:
> 
>> I will keep trying this until it's perfect, and I thank you for
>> the help.  When I resubmit this, would you like me to include your
>> sign-off line as well?
> 
> If the one I attached at the end of the message you are responding
> to looks fine to you, I'd just apply it without having you to
> reroll.
> 
>> Also, the end of the test script was not included in your message.  
> 
> Sorry, but I am not sure what you meant by this.
> 
> I reworked your example to make it the second test in an existing
> test script.  There are many existing tests after that so it is
> natural that we wouldn't see the end of the file in the patch
> context.
> 
>>> diff --git a/t/t7400-submodule-basic.sh b/t/t7400-submodule-basic.sh
>>> index 5ee97b0..a39d074 100755
>>> --- a/t/t7400-submodule-basic.sh
>>> +++ b/t/t7400-submodule-basic.sh
>>> @@ -18,6 +18,16 @@ test_expect_success 'setup - initial commit' '
>>> 	git branch initial
>>> '
>>> 
>>> +test_expect_success 'configuration parsing' '
>>> +	test_when_finished "rm -f .gitmodules" &&
>>> +	cat >.gitmodules <<-\EOF &&
>>> +	[submodule "s"]
>>> +		path
>>> +		ignore
>>> +	EOF
>>> +	test_must_fail git status
>>> +'
>>> +
>>> test_expect_success 'setup - repository in init subdirectory' '
>>> 	mkdir init &&
>>> 	(

  reply	other threads:[~2013-08-20  0:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16  1:51 [PATCH] Git segmentation faults if submodule path is empty Jharrod LaFon
2013-08-16  6:48 ` Jens Lehmann
2013-08-16 13:09   ` Jeff King
2013-08-16 13:14     ` Jeff King
2013-08-16 15:12       ` Jharrod LaFon
2013-08-16 17:59         ` Jharrod LaFon
2013-08-16 20:52           ` Jeff King
2013-08-19 16:26             ` Jharrod LaFon
2013-08-19 18:56               ` Junio C Hamano
2013-08-19 20:48                 ` Jeff King
     [not found]                 ` <30EC6002-1044-41E0-8700-1F210A6CA882@eyesopen.com>
2013-08-19 20:54                   ` Junio C Hamano
2013-08-20  0:26                     ` Jharrod LaFon [this message]
2013-08-16  7:50 ` Thomas Rast

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=D9B32897-9ABC-4F98-BE8B-CCC105FCAD9E@eyesopen.com \
    --to=jlafon@eyesopen.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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