git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCHv12 0/7] Expose submodule parallelism to the user

From
Stefan Beller <sbeller@google.com>
Date
Feb 18, 2016, 23:27 UTC
Message-ID
<CAGZ79kY7aYmDcz+JYwpzizfzRV3bUeN8TU-4jRjKqToJJTBHoA@mail.gmail.com>
In-Reply-To
<xmqqio1lehbp.fsf@gitster.mtv.corp.google.com>
On Thu, Feb 18, 2016 at 3:20 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 12 quoted lines
> Stefan Beller <sbeller@google.com> writes:
>
>> On Thu, Feb 18, 2016 at 3:12 PM, Stefan Beller <sbeller@google.com> wrote:
>>>> Unless you count "I want to write differently from what was
>>>> suggested" is a desirable thing to do, I do not see a point in
>>>> favouring the above that uses an extra variable and skip_prefix()
>>>> over what I gave you as "how about" patch.  But whatever.
>>>
>>> The skip_prefix was there before, so it stuck there.
>
> Sorry, but I thought this "parsing update strategy" was all new
> code.

I meant previous patches or in my mind. That's why I was hesitant to throw out the skip_prefix.

Show 24 quoted lines
>
>>> Also it seems a bit more high level to me hence easier to read,
>>> (though I am biased). I'll use your suggestion.
>>
>> and it doesn't crash when passing in value == NULL.
>> (We don't do that currently, just a side observation)
>
> Hmph.  If you pass str==NULL with prefix="!" to what we have below,
> I would think the first iteration would try to read from *str and do
> a bizarre thing.
>
> static inline int skip_prefix(const char *str, const char *prefix,
>                               const char **out)
> {
>         do {
>                 if (!*prefix) {
>                         *out = str;
>                         return 1;
>                 }
>         } while (*str++ == *prefix++);
>         return 0;
> }
>
> Puzzled.

And there I was asserting properties about methods without looking them up.

ok.
Previous: Junio C HamanoNext: Junio C Hamano
Message 13 of 14 in “[PATCHv12 0/7] Expose submodule parallelism to the user”
  1. Stefan BellerFeb 18, 2016
  2. 1/7 submodule-config: keep update strategy aroundStefan Beller, Feb 18, 2016
  3. 2/7 submodule-config: drop check against NULLStefan Beller, Feb 18, 2016
  4. 3/7 fetching submodules: respect `submodule.fetchJobs` config optionStefan Beller, Feb 18, 2016
  5. 4/7 submodule update: direct error message to stderrStefan Beller, Feb 18, 2016
  6. 5/7 git submodule update: have a dedicated helper for cloningStefan Beller, Feb 18, 2016
  7. 6/7 submodule update: expose parallelism to the userStefan Beller, Feb 18, 2016
  8. 7/7 clone: allow an explicit argument for parallel submodule clonesStefan Beller, Feb 18, 2016
  9. Junio C HamanoFeb 18, 2016
  10. Stefan BellerFeb 18, 2016
  11. Stefan BellerFeb 18, 2016
  12. Junio C HamanoFeb 18, 2016
  13. Stefan BellerFeb 18, 2016
  14. Junio C HamanoFeb 19, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.