All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Adolf <ryanadolf123@gmail.com>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Fwd: iw package typo in help command output
Date: Tue, 22 Oct 2019 00:21:26 -0700	[thread overview]
Message-ID: <CADh-Cm=bG2wV6Ccy3ATx3g=dsoXa6KAvxwBJ+pPxMSscaQ0AXA@mail.gmail.com> (raw)
In-Reply-To: <0f33cba3dd5fdcc4697c26e97e8f265c1bb9958c.camel@coelho.fi>

[-- Attachment #1: Type: text/plain, Size: 649 bytes --]

The patch is attached.
There's only one modified line in it: correcting the typo of timstamp
--> timestamp.

On Mon, Oct 21, 2019 at 1:07 PM Luca Coelho <luca@coelho.fi> wrote:
>
> On Mon, 2019-10-21 at 02:34 -0700, Ryan Adolf wrote:
> > Hello,
> >
> > First of all I'm not sure what the policy of this community is on
> > typos. It's my first time contributing to iw :) If you consider this
> > too minor to fix, I understand. The package has a lot of amazing stuff
> > to it.
>
> Just submit a patch! Then the maintainers will decide whether it's
> worth it or not.  I, particularly, don't see why it wouldn't be taken.
>
> --
> Cheers,
> Luca.
>

[-- Attachment #2: event.patch --]
[-- Type: text/x-patch, Size: 411 bytes --]

diff --git a/event.c b/event.c
index 100f644..4a932d1 100644
--- a/event.c
+++ b/event.c
@@ -1172,5 +1172,5 @@ static int print_events(struct nl80211_state *state,
 TOPLEVEL(event, "[-t|-r] [-f]", 0, 0, CIB_NONE, print_events,
 	"Monitor events from the kernel.\n"
 	"-t - print timestamp\n"
-	"-r - print relative timstamp\n"
+	"-r - print relative timestamp\n"
 	"-f - print full frame for auth/assoc etc.");

  reply	other threads:[~2019-10-22  7:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADh-Cm=umBWCkz41-e0-PDnDrbpfQi_PRdT--SePmQLCqj5rwg@mail.gmail.com>
2019-10-21  9:34 ` Fwd: iw package typo in help command output Ryan Adolf
2019-10-21 20:07   ` Luca Coelho
2019-10-22  7:21     ` Ryan Adolf [this message]
2019-10-22  7:38       ` Kalle Valo
2019-10-22  7:48       ` Toke Høiland-Jørgensen

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='CADh-Cm=bG2wV6Ccy3ATx3g=dsoXa6KAvxwBJ+pPxMSscaQ0AXA@mail.gmail.com' \
    --to=ryanadolf123@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luca@coelho.fi \
    /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.