From: Stefan Beller <sbeller@google.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] clone: don't use an integer as a NULL pointer
Date: Wed, 25 May 2016 16:30:50 -0700 [thread overview]
Message-ID: <CAGZ79kaEtayuY8ZdB5hD_uYK8qZKQ1kiP3tPchjUm4k_HuVyow@mail.gmail.com> (raw)
In-Reply-To: <5746316E.8020902@ramsayjones.plus.com>
On Wed, May 25, 2016 at 4:12 PM, Ramsay Jones
<ramsay@ramsayjones.plus.com> wrote:
>
> Signed-off-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
> ---
>
> Hi Stefan,
>
> If you need to re-roll your 'sb/submodule-default-paths' branch, could
> you please squash this into the relevant patch. (commit 8efbe28b,
> "clone: add --init-submodule=<pathspec> switch", 23-05-2016).
>
> Thanks!
>
> ATB,
> Ramsay Jones
Thanks for pointing out!
I am sorry for having you write me these emails;
Out of curiosity, how much of this is manual work and how
much did you automate of this?
>
> builtin/clone.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/builtin/clone.c b/builtin/clone.c
> index 22b6eac..a056f72 100644
> --- a/builtin/clone.c
> +++ b/builtin/clone.c
> @@ -925,7 +925,7 @@ int cmd_clone(int argc, const char **argv, const char *prefix)
> struct strbuf sb = STRBUF_INIT;
> for_each_string_list_item(item, &init_submodules) {
> strbuf_addf(&sb, "submodule.defaultUpdatePath=%s", item->string);
> - string_list_append(&option_config, strbuf_detach(&sb, 0));
> + string_list_append(&option_config, strbuf_detach(&sb, NULL));
> }
> }
>
> --
> 2.8.0
next prev parent reply other threads:[~2016-05-25 23:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 23:12 [PATCH] clone: don't use an integer as a NULL pointer Ramsay Jones
2016-05-25 23:30 ` Stefan Beller [this message]
2016-05-26 0:32 ` Ramsay Jones
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=CAGZ79kaEtayuY8ZdB5hD_uYK8qZKQ1kiP3tPchjUm4k_HuVyow@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=ramsay@ramsayjones.plus.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).