From: Brian Norris <briannorris@chromium.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: iw release cadence?
Date: Fri, 1 Feb 2019 13:46:06 -0800 [thread overview]
Message-ID: <CA+ASDXMVAP4CsE=vaomOn5mu_uAM0jc3jvWGzaVPFFif4kTX+Q@mail.gmail.com> (raw)
Hi Johannes,
Is there any sort of release cadence to the iw tool? Or is it pretty
arbitrary? I'm curious, since it's been more than a year since the
"v4.14" release. I'd like to package up bugfixes and a few features,
but it'd be much nicer to just pull a new official tag/tarball than to
drop a bunch of individual patches into my build system. If you're
going to tag something soon though, I can...just wait for you :)
More bluntly: can I haz release please?
Regards,
Brian
next reply other threads:[~2019-02-01 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 21:46 Brian Norris [this message]
2019-02-01 21:54 ` iw release cadence? Johannes Berg
2019-02-01 22:09 ` Johannes Berg
2019-02-01 22:17 ` Brian Norris
2019-02-01 22:18 ` Johannes Berg
2019-02-01 22:23 ` Johannes Berg
2019-08-04 22:25 ` Kirtika Ruchandani
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='CA+ASDXMVAP4CsE=vaomOn5mu_uAM0jc3jvWGzaVPFFif4kTX+Q@mail.gmail.com' \
--to=briannorris@chromium.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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 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).