Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 15 Oct 2011 18:53:03 -0400 (EDT)
From:      Benjamin Kaduk <kaduk@MIT.EDU>
To:        Garrett Cooper <yanegomi@gmail.com>
Cc:        Niclas Zeising <niclas.zeising@gmail.com>, freebsd-doc@freebsd.org
Subject:   Re: docs/160696: style(9) should be mentioned in the devs&#39; handbook
Message-ID:  <alpine.GSO.1.10.1110151851460.882@multics.mit.edu>
In-Reply-To: <CAGH67wT3W0piFjX328ensJiUrvw2tVK5ufMtSF90of97wwhs7w@mail.gmail.com>
References:  <201110121030.p9CAUDxd032245@freefall.freebsd.org> <alpine.GSO.1.10.1110132355240.882@multics.mit.edu> <alpine.BSF.2.00.1110132212210.51180@wonkity.com> <CAGH67wQBtWPYKMURtd0mp4HnZC3gn3pg2GHu0wK%2BZjg-DtL5-Q@mail.gmail.com> <alpine.BSF.2.00.1110140007150.51585@wonkity.com> <CAGH67wT3W0piFjX328ensJiUrvw2tVK5ufMtSF90of97wwhs7w@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---559023410-1032669857-1318719122=:882
Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-15; FORMAT=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-ID: <alpine.GSO.1.10.1110151852091.882@multics.mit.edu>

On Fri, 14 Oct 2011, Garrett Cooper wrote:

> On Thu, Oct 13, 2011 at 11:37 PM, Warren Block <wblock@wonkity.com> wrote=
:
>> On Thu, 13 Oct 2011, Garrett Cooper wrote:
>>
>>> On Thu, Oct 13, 2011 at 9:13 PM, Warren Block <wblock@wonkity.com> wrot=
e:
>>>>
>>>> On Fri, 14 Oct 2011, Benjamin Kaduk wrote:
>>>>
>>>>> The overall paragraph feels a bit odd, though; maybe like it's writte=
n
>>>>> in
>>>>> a more informal style than I would expect? =A0A more standard dry,
>>>>> technical
>>>>> writing version might be:
>>>>> %%%%%%%%%%
>>>>> <para>When working in a large codebase such as the &os; source, it is
>>>>> important to adhere to a common coding style. =A0This provides unifor=
mity
>>>>
>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 ^^^^^^
>>>> "conform" might be better here.
>>>
>>> I'm usually not touchy feely about wording like this, but unless the
>>> rest of the document is worded in such a standoffish / cold manner, I
>>> would just keep things polite and neutral. "Conform" sounds really
>>> pushy and "When working in a..." sounds condescending in my opinion.
>>
>> Here's a rewrite:
>>
>> <para>Consistent coding style is extremely important, particularly with
>> =A0large projects like &os;. =A0Code should follow the &os; coding style=
s
>> =A0described in &man.style.9;, and &man.style.Makefile.5;.</para>
>
> Sounds ok.

No arguments, here.
(Well, except for Garrett's mailer's mangling of the whitespace ...)

-Ben
---559023410-1032669857-1318719122=:882--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1110151851460.882>