Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 1/1] yad: new package
Date: Thu, 29 Oct 2015 09:09:47 +0000	[thread overview]
Message-ID: <5631E25B.5020103@imgtec.com> (raw)
In-Reply-To: <CALe+oY-dFj4aCxv3Nes5N7uH0B5LbcEFuKnMDd4No_YNT4nFdg@mail.gmail.com>

Dear James Knight,

On 10/28/2015 09:34 PM, James Knight wrote:
> Vincent,
> 
> First off, thanks for reviewing/testing (as always).
> 
> On Tue, Oct 27, 2015 at 10:41 AM, Vicente Olivert Riera
> <Vincent.Riera@imgtec.com> wrote:
>>> +     help
>>> +       YAD (yet another dialog) is a tool for create graphical dialogs from
>>
>> That line exceeds the 72 characters limit considering 8-characters-wide
>> tabs.
> 
> Sorry, I'm confused. I only moved the word "from" into the lined based
> off your previous suggestion:

You are totally right and I apologize for that. This is totally my
fault. It seems that in the Buildroot project tabs are considered as 8
characters wide. I didn't know that when I made that suggestion to you,
but in my defense I have to say that is not documented anywhere.

Regards,

Vincent.

> On Wed, Oct 7, 2015 at 6:08 AM, Vicente Olivert Riera
> <Vincent.Riera@imgtec.com> wrote:
>>> +     select BR2_PACKAGE_LIBGLIB2
>>> +     help
>>> +       YAD (yet another dialog) is a tool for create graphical dialogs
>>> +       from shell scripts.
>>
>> The word "from" still fits in the first line as it will not exceed the
>> 72 characters limit.
> 
> Am I missing something?
> 

      reply	other threads:[~2015-10-29  9:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 23:10 [Buildroot] [PATCH v5 1/1] yad: new package James Knight
2015-10-27 14:41 ` Vicente Olivert Riera
2015-10-28 21:34   ` James Knight
2015-10-29  9:09     ` Vicente Olivert Riera [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=5631E25B.5020103@imgtec.com \
    --to=vincent.riera@imgtec.com \
    --cc=buildroot@busybox.net \
    /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