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

Re: [PATCHv20 00/12] Expose submodule parallelism to the user

From
Stefan Beller <sbeller@google.com>
Date
Feb 29, 2016, 20:40 UTC
Message-ID
<CAGZ79ka7Wrc4kzXWwi8c+6JC0FVC45g=fu-F6QxXFe37sm5GMQ@mail.gmail.com>
In-Reply-To
<20160229193222.GX28749@google.com>
On Mon, Feb 29, 2016 at 11:32 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
Show 6 quoted lines
> Stefan Beller wrote:
>
>> I added your suggestions as amending and as a new patch.
>
> I think we're at the point where patches on top would work better.  I
> admit I was a little scared to see another reroll.

Yeah I am a bit scared too, so I'll do patches on top for further fixes after one last reroll, fixing the issues below.

Show 29 quoted lines
>
> [...]
>> --- a/builtin/submodule--helper.c
>> +++ b/builtin/submodule--helper.c
>> @@ -299,10 +299,10 @@ static int prepare_to_clone_next_submodule(const struct cache_entry *ce,
>>
>>       if (ce_stage(ce)) {
>>               if (suc->recursive_prefix) {
>> -                     strbuf_addf(out, "Skipping unmerged submodule %s/%s\n",
>> +                     strbuf_addf(out,_("Skipping unmerged submodule %s/%s\n"),
>
> Missing space after comma.
>
> Usual practice for i18n would be something like
>
>         struct strbuf path = STRBUF_INIT;
>         if (suc->recursive_prefix)
>                 strbuf_addf(&path, "%s/%s", suc->recursive_prefix, ce->name);
>         else
>                 strbuf_addstr(&path, ce->name);
>
>         strbuf_addf(out, _("Skipping unmerged submodule %s"), path.buf);
>         strbuf_addch(out, '\n');
>         strbuf_release(&path);
>
> Reasons:
>  - translators shouldn't have to worry about the trailing newline
>  - minimizing number of strings to translate
>  - minimizing the chance that a translator typo produces an invalid path
Thanks for reminding me of that practice!
Show 14 quoted lines
>
> [...]
>> @@ -319,7 +319,7 @@ static int prepare_to_clone_next_submodule(const struct cache_entry *ce,
>>       if (suc->update.type == SM_UPDATE_NONE
>>           || (suc->update.type == SM_UPDATE_UNSPECIFIED
>>               && sub->update_strategy.type == SM_UPDATE_NONE)) {
>> -             strbuf_addf(out, "Skipping submodule '%s'\n",
>> +             strbuf_addf(out, _("Skipping submodule '%s'\n"),
>>                           displaypath);
>
> Same issue here with the trailing \n.
>
> If the strbuf_addf + strbuf_addch('\n') pattern is common enough, we
> could introduce a helper (e.g. strbuf_addf_nl) to save typing.
I don't think it is common enough yet.

Thanks, Stefan

>
> Thanks and hope that helps,
> Jonathan
Previous: Jonathan NiederNext: Junio C Hamano
Message 15 of 16 in “[PATCHv20 00/12] Expose submodule parallelism to the user”
  1. Stefan BellerFeb 29, 2016
  2. 01/12 submodule-config: keep update strategy aroundStefan Beller, Feb 29, 2016
  3. 02/12 submodule-config: drop check against NULLStefan Beller, Feb 29, 2016
  4. 03/12 fetching submodules: respect `submodule.fetchJobs` config optionStefan Beller, Feb 29, 2016
  5. 04/12 submodule update: direct error message to stderrStefan Beller, Feb 29, 2016
  6. 05/12 run_processes_parallel: treat output of children as byte arrayStefan Beller, Feb 29, 2016
  7. 06/12 run-command: expose default_{start_failure, task_finished}Stefan Beller, Feb 29, 2016
  8. 07/12 run_processes_parallel: rename parameters for the callbacksStefan Beller, Feb 29, 2016
  9. 08/12 run_processes_parallel: correctly terminate callbacks with an LFStefan Beller, Feb 29, 2016
  10. 09/12 git submodule update: have a dedicated helper for cloningStefan Beller, Feb 29, 2016
  11. 10/12 submodule helper: remove double 'fatal: ' prefixStefan Beller, Feb 29, 2016
  12. 11/12 submodule update: expose parallelism to the userStefan Beller, Feb 29, 2016
  13. 12/12 clone: allow an explicit argument for parallel submodule clonesStefan Beller, Feb 29, 2016
  14. Jonathan NiederFeb 29, 2016
  15. Stefan BellerFeb 29, 2016
  16. Junio C HamanoFeb 29, 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.