From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc:it_IT: add translations in process/
Date: Wed, 06 Feb 2019 23:55:38 +0100 [thread overview]
Message-ID: <aa09cd3309bc9787b6ff3b1331508bb2@vaga.pv.it> (raw)
In-Reply-To: <2146324.8BP4ZdZamE@pcbe13614>
On 2019-01-21 09:11, Federico Vaga wrote:
> On Monday, January 21, 2019 2:56:17 AM CET Jonathan Corbet wrote:
>> On Sat, 19 Jan 2019 23:13:41 +0100
>>
>> Federico Vaga <federico.vaga@vaga.pv.it> wrote:
>> > This patch adds the Italian translation for the following documents
>> > in Documentation/process:
>> >
>> > - applying-patches
>> > - submit-checklist
>> > - submitting-drivers
>> > - changes
>> > - stable api nonsense
>> >
>> > Signed-off-by: Federico Vaga <federico.vaga@vaga.pv.it>
>>
>> In general, this looks good. One thing jumped at me, though...(OK,
>> more
>>
>> than one, but only one to fix):
>> > +Perl
>> > +----
>> > +
>> > +Per compilare il kernel vi servirà perl 5 e i seguenti moduli
>> > ``Getopt::Long``, +``Getopt::Std``, ``File::Basename``, e ``File::Find``.
>>
>> Didn't Rob Landley go though some considerable pain a while back to
>> eliminate Perl from the basic kernel build? This, perhaps, should
>> come out
>> of the original. (As long as it's still there, it makes sense to be
>> in the
>> translation, of course).
>
> I can have a deeper look and try to fix the original document too
>
>>
>> > +Modifiche architetturali
>> > +------------------------
>> > +
>> > +DevFS è stato reso obsoleto da udev
>> > +(http://www.kernel.org/pub/linux/utils/kernel/hotplug/)
>> > +
>> > +Il supporto per UID a 32-bit è ora disponibile. Divertitevi!
>>
>> Speaking of stuff that should come out of the original...this is not
>> exactly news at this point...
>
> Well, generally speaking this document mix things from the past and the
> "present". Probably it requires a review.
I am having a look at this document and I am wandering if this is an
useful
document? Clearly I see value in the table with all requirements
summarised,
but I do not see it for the rest of the document.
So, I propose to actually rename change.rst to requirements.rst and
remove
everything but the requirements chapter and the links.
(proposal)
Release changes probably need a CHANGELOG file, to describe new and
deprecated things.
And information about tools should be in other document.
(/proposal)
What do you think?
>> Meanwhile, here is the thing that actually needs to be fixed:
>> > +Raiserfsprogs
>> > +-------------
>> > +
>> > +Il pacchetto raiserfsprogs dovrebbe essere usato con raiserfs-3.6.x
>> > (Linux
>> > +kernel 2.4.x). Questo è un pacchetto combinato che contiene versioni
>> > +funzionanti di ``mkreiserfs``, ``resize_reiserfs``, ``debugreiserfs`` e
>> > +``reiserfsck``. Questi programmi funzionano sulle piattaforme i386 e
>> > alpha.
>> Even in Italian, I believe that 'Reiser" is spelled "Reiser"...
>
> oops, your are right. I will fix this and send a V2 patch. Then I will
> have a
> look at the original document and try to update it
>
>> Thanks,
>>
>> jon
--
Federico Vaga
http://www.federicovaga.it/
next prev parent reply other threads:[~2019-02-06 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 22:13 Federico Vaga
2019-01-21 1:56 ` Jonathan Corbet
2019-01-21 8:11 ` Federico Vaga
2019-02-06 22:55 ` Federico Vaga [this message]
2019-02-07 0:18 ` Jonathan Corbet
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=aa09cd3309bc9787b6ff3b1331508bb2@vaga.pv.it \
--to=federico.vaga@vaga.pv.it \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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
Powered by JetHome