From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Denis Barbier <bouzim-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [Patch] Fix groff syntax
Date: Mon, 27 Sep 2010 07:59:01 +0200 [thread overview]
Message-ID: <AANLkTinxJdrMsObXZ9KYGqc6yP+V-p=yJS4RNWWiOW=a@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik3+Wx3-dOnPmeCZoz_RLRjGSXbWRo=cW7vKR7k-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hello Denis,
On Sun, Sep 26, 2010 at 6:00 PM, Denis Barbier <bouzim-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On 2010/9/26 Michael Kerrisk wrote:
>> On Sun, Sep 26, 2010 at 12:09 PM, Denis Barbier <bouzim-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>> Hello,
>>>
>>> Here is a syntax.patch file to fix 2 groff issues, and another patch
>>> to fix trivial issues with mknotat.2 and rand.3.
>>
>> Thanks Denis. All changes applied for 3.28.
>>
>> So, a question. How close is the Debian French translation behind me?
>> It looks like: very close. (Are there any still untranslated pages?)
>
> Hello Michael,
>
> We are indeed very close ;)
> 3.24 man-pages (26-Feb-2010) man-pages-fr (28-Feb-2010)
> 3.25 man-pages (20-Jun-2010) man-pages-fr (11-Jul-2010)
> 3.26 man-pages (05-Sep-2010) man-pages-fr (13-Sep-2010)
> All pages are translated except mdoc.samples.7, this page is huge and
> not really useful IMHO.
Excellent.
Would you like to supply a small piece of text for
http://www.kernel.org/doc/man-pages/translations.html
?
> We follow closely your git repository to translate HEAD, so that we
> have only a small amount of work left when you release. (Except when
> you don't push for a couple of weeks and send dozens of large commits
> in a row ;))
I'll try to be better. From now on, you can expect to be doing a bit
more translation work.
>> If so, that's great, since it's good to to know I have sort of
>> checking that you are doing with these packages.
>
> Right, and when you can, please push your changes as soon as possible,
> we may catch those mistakes before you release. But it is up to you,
> really, we are happy with your current workflow, it does not matter
> much if our release is delayed by 2 days instead of 2 weeks.
Okay.
thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-09-27 5:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 10:09 [Patch] Fix groff syntax Denis Barbier
[not found] ` <AANLkTinn0cN2w2+u0LuZWQcWZgCdEN6w=q3jq9zzLUr6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-09-26 14:08 ` Michael Kerrisk
[not found] ` <AANLkTi=_UY9By=Vf8Jv_M4BK8M6ED318j9rhiYkVT5Sk-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-09-26 16:00 ` Denis Barbier
[not found] ` <AANLkTik3+Wx3-dOnPmeCZoz_RLRjGSXbWRo=cW7vKR7k-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-09-27 5:59 ` Michael Kerrisk [this message]
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='AANLkTinxJdrMsObXZ9KYGqc6yP+V-p=yJS4RNWWiOW=a@mail.gmail.com' \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=bouzim-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).