All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Miguel Ángel Arruga Vivas" <rosen644835@gmail.com>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: grub-devel@gnu.org,  Glenn Washburn <development@efficientek.com>
Subject: Re: [PATCH 0/1] PRI* translation issues.
Date: Thu, 15 Apr 2021 10:58:38 +0200	[thread overview]
Message-ID: <87im4nzzy9.fsf@gmail.com> (raw)
In-Reply-To: <20210408124006.c53jdut2xtcdtapd@tomti.i.net-space.pl> (Daniel Kiper's message of "Thu, 8 Apr 2021 14:40:06 +0200")

Hi,

Daniel Kiper <dkiper@net-space.pl> writes:

[...]
> Signed-off-by: Miguel Ángel Arruga Vivas <rosen644835@gmail.com>
>
> I can add this for you before committing the patch.

That'd be great, thank you.

>> I added a description of the change there too instead of only making
>> the reference to the manual, but certainly I don't know what SOB means
>
> Great! Though I will tweak it a bit before committing.

Thanks again. I'm not a great writer even on my mother tongue, any
improvement is always welcome.

[...]
>> I wasn't quite sure about this, as the column count goes high on my
>> Emacs, should I remove some indentation?  Perhaps three lines could be
>> another compromise with N_ and rel_info on separate lines as the other
>> code?
>
> Yep.

Which one of the three options do you mean? In any case, it goes without
saying that I'm thankful to any tweak performed before pushing the patch
to the working branch.

Best regards,
Miguel


  reply	other threads:[~2021-04-15  8:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03 13:33 [PATCH 0/1] PRI* translation issues Miguel Ángel Arruga Vivas
2021-04-03 13:33 ` [PATCH 1/1] i18n: Format large integers before the translation message Miguel Ángel Arruga Vivas
2021-04-03 22:12 ` [PATCH 0/1] PRI* translation issues Mihai Moldovan
2021-04-15  9:02   ` Miguel Ángel Arruga Vivas
2021-04-08 12:40 ` Daniel Kiper
2021-04-15  8:58   ` Miguel Ángel Arruga Vivas [this message]
2021-04-20 14:02     ` Daniel Kiper

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=87im4nzzy9.fsf@gmail.com \
    --to=rosen644835@gmail.com \
    --cc=development@efficientek.com \
    --cc=dkiper@net-space.pl \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.