From: "John W. Linville" <linville@tuxdriver.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Kalle Valo <kvalo@adurom.com>,
Xose Vazquez Perez <xose.vazquez@gmail.com>,
"Luis R. Rodriguez" <mcgrof@frijolero.org>,
wireless-regdb@lists.infradead.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] wireless-regdb: Update regulatory rules for ES (Spain) on 5GHz and 2.4GHz
Date: Mon, 13 Aug 2012 10:04:41 -0400 [thread overview]
Message-ID: <20120813140441.GA10529@tuxdriver.com> (raw)
In-Reply-To: <502908A9.2010803@broadcom.com>
On Mon, Aug 13, 2012 at 04:01:13PM +0200, Arend van Spriel wrote:
> On 07/09/2012 03:14 PM, Kalle Valo wrote:
> > "Arend van Spriel" <arend@broadcom.com> writes:
> >
> >> Just a general remark not specific to this patch. The commit message
> >> often contains a source reference. I think it would be useful to have
> >> this reference in the database as well so people validating it do not
> >> need to do the digging using 'git blame'. Does that make sense?
> >
> > Yes :)
> >
> > IMHO makes a lot easier to validate the entries.
> >
>
> Luis, John,
>
> What are your thoughts on my remark above?
It seems reasonable to me. OTOH, it could lead to a lot of clutter
in the database file...? I guess it is a matter of judgment.
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:[~2012-08-13 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 0:41 [PATCH v2] wireless-regdb: Update regulatory rules for ES (Spain) on 5GHz and 2.4GHz Xose Vazquez Perez
2012-07-04 0:49 ` Luis R. Rodriguez
2012-07-04 1:05 ` Xose Vazquez Perez
2012-07-04 6:01 ` Arend van Spriel
2012-07-09 13:14 ` Kalle Valo
2012-08-13 14:01 ` Arend van Spriel
2012-08-13 14:04 ` 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=20120813140441.GA10529@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=arend@broadcom.com \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@frijolero.org \
--cc=wireless-regdb@lists.infradead.org \
--cc=xose.vazquez@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).