From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [ANN] wireless-regdb: master-2011-04-28
Date: Thu, 12 May 2011 15:34:16 +0200 [thread overview]
Message-ID: <1305207256.3461.31.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20110512132146.GK2490@tuxdriver.com> (sfid-20110512_153105_401955_5B10C3ED)
On Thu, 2011-05-12 at 09:21 -0400, John W. Linville wrote:
> Weird, this took a while...
Oh, I know why. There were local changes in the tree that generates
these emails and thus it never pulled properly.
johannes
prev parent reply other threads:[~2011-05-12 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 3:10 [ANN] wireless-regdb: master-2011-04-28 wireless
2011-05-12 13:21 ` John W. Linville
2011-05-12 13:34 ` Johannes Berg [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=1305207256.3461.31.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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