From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: ss/submodule-add-in-c, was Re: What's cooking in git.git (Dec 2020, #05; Mon, 28)
Date: Tue, 05 Jan 2021 14:57:02 -0800 [thread overview]
Message-ID: <xmqqturvxa9t.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2101051640150.2213@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Tue, 5 Jan 2021 16:41:38 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi Junio,
>
> On Mon, 28 Dec 2020, Junio C Hamano wrote:
>
>> * ss/submodule-add-in-c (2020-12-15) 3 commits
>> . t7400: add test to check 'submodule add' for tracked paths
>> . submodule: port submodule subcommand 'add' from shell to C
>> . dir: change the scope of function 'directory_exists_in_index()'
>>
>> "git submodule add" being rewritten in C.
>>
>> Expecting a reroll.
>> The patches are split incorrectly; part of 1/3 belongs to 2/3
>> cf. <nycvar.QRO.7.76.6.2012190104140.56@tvgsbejvaqbjf.bet>
>> It seems to introduce a segfault on 'seen'.
>> cf. <xmqqft3xflw7.fsf@gitster.c.googlers.com>
>
> Maybe nycvar.QRO.7.76.6.2012190104140.56@tvgsbejvaqbjf.bet would be a
> better reference,...
That is the first message-id referenced in the above, isn't it?
next prev parent reply other threads:[~2021-01-05 22:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 19:09 What's cooking in git.git (Dec 2020, #05; Mon, 28) Junio C Hamano
2020-12-29 1:35 ` Felipe Contreras
2021-01-06 5:55 ` Junio C Hamano
2020-12-29 8:32 ` Christian Couder
2021-01-05 15:41 ` ss/submodule-add-in-c, was " Johannes Schindelin
2021-01-05 22:57 ` Junio C Hamano [this message]
2021-01-07 23:23 ` Johannes Schindelin
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=xmqqturvxa9t.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--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).