From: "John W. Linville" <linville@tuxdriver.com>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
Nick Kossifidis <mickflemm@gmail.com>,
Nick Kossifidis <mick@madwifi-project.org>,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
mcgrof@gmail.com, me@bobcopeland.com, nbd@openwrt.org
Subject: Re: [PATCH 2/7] ath5k: Read Spur channels from EEPROM
Date: Mon, 20 Apr 2009 14:25:25 -0400 [thread overview]
Message-ID: <20090420182524.GE3369@tuxdriver.com> (raw)
In-Reply-To: <87k55lf7hs.fsf@litku.valot.fi>
On Thu, Apr 16, 2009 at 09:16:47AM +0300, Kalle Valo wrote:
> Jiri Slaby <jirislaby@gmail.com> writes:
>
> > On 04/16/2009 03:04 AM, Johannes Berg wrote:
> >> On Thu, 2009-04-16 at 03:51 +0300, Nick Kossifidis wrote:
> >>> ACK, are 80 cols ok ?
> >>
> >> I don't know if there's a standard on that, I tend to use around 60-70,
> >> but 80 seems good too. It's not just the "doesn't fit terminal" argument
> >> anyway, it's much easier to read if it's less.
> >
> > When one uses git log, it gets moved few (4) columns to the right. So
> > something little less than 76 is usually preferred :).
>
> I think in usenet 72 characters was the recommended width, right? That
> way quoting was also easier.
72 is my vote...thanks!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2009-04-20 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 0:24 [PATCH 2/7] ath5k: Read Spur channels from EEPROM Nick Kossifidis
2009-04-16 0:25 ` Johannes Berg
2009-04-16 0:51 ` Nick Kossifidis
2009-04-16 1:04 ` Johannes Berg
2009-04-16 6:14 ` Jiri Slaby
2009-04-16 6:16 ` Kalle Valo
2009-04-20 18:25 ` John W. Linville [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=20090420182524.GE3369@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=me@bobcopeland.com \
--cc=mick@madwifi-project.org \
--cc=mickflemm@gmail.com \
--cc=nbd@openwrt.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.