From: Laszlo Ersek <lersek@redhat.com>
To: Jordan Justen <jordan.l.justen@intel.com>, edk2-devel@lists.01.org
Subject: Re: [PATCH v2 1/1] OvmfPkg : QemuFwCfgLib: Use BusMasterCommandBuffer to map FW_CFG_DMA_ACCESS
Date: Thu, 10 Aug 2017 21:48:16 +0200 [thread overview]
Message-ID: <bc1a5483-e47f-e8a9-a3b2-d328ed5e26f0@redhat.com> (raw)
In-Reply-To: <150239020750.4777.16972339809591983854@jljusten-skl>
On 08/10/17 20:36, Jordan Justen wrote:
> On 2017-08-04 13:25:09, Laszlo Ersek wrote:
>>>
>>> I have another reason why going beyond 80 is not a good idea for code
>>> that doesn't apply to normal reading. If you need ~120 columns visible
>>> to view some lines, then most lines will end up having a lot of wasted
>>> horizontal whitespace because they can commonly fit into 80 columns.
>>
>> One reason I dislike the "all arguments on separate lines" rule is just
>> this -- it wastes perfectly good horizontal space, and eats up precious
>> vertical space.
>>
>> We have a patch submission process for our documents now,
>
> I think I agree about the multiple args/multiple lines issue. I guess
> you could try to submit a code style doc change, but I'm not sure how
> controversial it might be.
>
>> but I don't
>> think maintainers of other Pkgs would bother with following and
>> enforcing a stricter 80 columns rule, even if we got it codified. :/
>
> I still think we should have it written stricter even if it isn't
> always followed. It could be a step in the right direction.
OK, I'm tagging this for later... Not sure how much later ;)
Thanks
Laszlo
prev parent reply other threads:[~2017-08-10 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 16:09 [PATCH v2 0/1] OvmfPkg/QemuFwCfgLib: Use BusMasterCommandBuffer to map FW_CFG_DMA_ACCESS Brijesh Singh
2017-08-03 16:10 ` [PATCH v2 1/1] OvmfPkg : QemuFwCfgLib: " Brijesh Singh
2017-08-03 20:51 ` Laszlo Ersek
2017-08-03 22:07 ` Brijesh Singh
2017-08-03 22:27 ` Laszlo Ersek
2017-08-04 17:08 ` Jordan Justen
2017-08-04 20:25 ` Laszlo Ersek
2017-08-10 18:36 ` Jordan Justen
2017-08-10 19:48 ` Laszlo Ersek [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-list 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=bc1a5483-e47f-e8a9-a3b2-d328ed5e26f0@redhat.com \
--to=devel@edk2.groups.io \
/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