From: Jonathan Corbet <firstname.lastname@example.org> To: Federico Vaga <email@example.com> Cc: Alessia Mantegazza <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org Subject: Re: [PATCH 0/3] doc:it_IT: update italian documentation Date: Tue, 20 Nov 2018 09:16:10 -0700 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Fri, 9 Nov 2018 00:24:14 +0100 Federico Vaga <email@example.com> wrote: > In this small patch set there is the V3 of > "doc:it_IT: add some process/* translations" in which I fixed > the recent conflicts in docs-next. > I took the occasion to add other two simple patches that fix: > - a missing translation in locking.rst > - apply a patch from the official documentation to the italian one OK, I have applied the set, apologies for taking so long. I do have one request: there are an awful lot of entries that simply say "ancora da tradurre" in here; those are not going to bring much joy to your readers. Can I ask that you try to reduce those in number, either by doing the work or concluding that it won't happen and just removing them? No timelines or anything - I'd just be happy to see the work go in that direction. Thanks, jon
next prev parent reply other threads:[~2018-11-20 16:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-11-08 23:24 Federico Vaga 2018-11-08 23:24 ` [PATCH V3 1/3] doc:it_IT: add some process/* translations Federico Vaga 2018-11-08 23:24 ` [PATCH 2/3] doc:it_IT: fix locking.rst section title Federico Vaga 2018-11-08 23:24 ` [PATCH 3/3] doc:it_IT:doc-guide: fix reference to foobar Federico Vaga 2018-11-20 16:16 ` Jonathan Corbet [this message] 2018-11-21 0:24 ` [PATCH 0/3] doc:it_IT: update italian documentation Federico Vaga
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH 0/3] doc:it_IT: update italian documentation' \ /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
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).