Git development
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Jharrod LaFon <jlafon@eyesopen.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] Git segmentation faults if submodule path is empty.
Date: Fri, 16 Aug 2013 16:52:47 -0400	[thread overview]
Message-ID: <20130816205246.GA6487@sigill.intra.peff.net> (raw)
In-Reply-To: <0C422E09-EE33-4C3F-91D3-F6007F743A38@eyesopen.com>

On Fri, Aug 16, 2013 at 10:59:35AM -0700, Jharrod LaFon wrote:

> Here is an updated patch with a test.

Bits like this that should not be part of the commit message should
either go after the "---" lines near the diffstat, or should come before
a scissors line, like:

  Here is my new patch.

  -- >8 --
  Git segmentation faults etc...

That way git-am can do the right thing, and the maintainer does not have
to fix up your patch by hand.

> diff --git a/submodule.c b/submodule.c
> index 1821a5b..1e4acfd 100644
> --- a/submodule.c
> +++ b/submodule.c
> @@ -134,6 +134,9 @@ int parse_submodule_config_option(const char *var, const char *value)
>  		return 0;
>  
>  	if (!strcmp(key, "path")) {
> +        if (!value)
> +            return config_error_nonbool(var);

Your indentation looks like two spaces here, which does not match the
rest of the block. It should be one tab.

> @@ -151,6 +154,9 @@ int parse_submodule_config_option(const char *var, const char *value)
>  	} else if (!strcmp(key, "ignore")) {
>  		char *name_cstr;
>  
> +        if (!value)
> +            return config_error_nonbool(var);
> +

Ditto here.

> diff --git a/t/t1307-null-submodule-path.sh b/t/t1307-null-submodule-path.sh
> new file mode 100644
> index 0000000..eeda2cb
> --- /dev/null
> +++ b/t/t1307-null-submodule-path.sh
> @@ -0,0 +1,16 @@
> +#!/bin/sh
> +
> +test_description='test empty submodule path'
> +. ./test-lib.sh
> +
> +setup() {
> +    (printf "[submodule \"test\"]\n" && 
> +    printf "  path\n" &&
> +    printf "  url") >.gitmodules
> +}

You can use single-quotes to avoid having to backslash the embedded
double-quotes. And I do not see any reason to use printf rather than the
more readable echo, which can drop the "\n".

And is there any point in having the "url" field?  The presence of a
valueless bool "path" should be enough, no? It may be easier to see what
it is we are testing without the extraneous parameter.

With those changes, you could even put it all on one line:

  echo '[submodule "test"] path' >.gitmodules

-Peff

  reply	other threads:[~2013-08-17  0:11 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 [this message]
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
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=20130816205246.GA6487@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=jlafon@eyesopen.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