From: Rusty Russell <rusty@rustcorp.com.au>
To: kuebelr@email.uc.edu
Cc: torvalds@transmeta.com, marcelo@conectiva.com.br,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spelling mistakes
Date: Mon, 29 Apr 2002 13:28:31 +1000 [thread overview]
Message-ID: <20020429132831.44bba537.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20020423195052.GA967@cartman>
On Tue, 23 Apr 2002 15:50:52 -0400
kuebelr@email.uc.edu wrote:
> Fixes a few spelling mistakes in documentation (arch/i386/boot/setup.S,
> Documentation/sysrq.txt). Pretty boring. This is against 2.4.19-pre7,
> but also applies to 2.5.9.
>
> Thanks.
> Rob.
You might want to send each of these individually to the Trivial Patch Monkey,
for tracking and retransmission:
trivial at rustcorp.com.au
Thanks,
Rusty.
--
there are those who do and those who hang on and you don't see too
many doers quoting their contemporaries. -- Larry McVoy
prev parent reply other threads:[~2002-04-29 3:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 19:50 [PATCH] spelling mistakes kuebelr
2002-04-29 3:28 ` Rusty Russell [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=20020429132831.44bba537.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=kuebelr@email.uc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.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