From: Michal Marek <mmarek@suse.cz>
To: Warren Turkal <wt@penguintechs.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: possible typo
Date: Tue, 10 Jun 2014 14:16:54 +0200 [thread overview]
Message-ID: <5396F736.4080901@suse.cz> (raw)
In-Reply-To: <53956B28.7040404@penguintechs.org>
On 2014-06-09 10:07, Warren Turkal wrote:
> commit 4ce2f36b4b06b7df569b1875c7ab834270786882
> Author: Warren Turkal <wt@penguintechs.org>
> Date: Sun Jun 8 22:19:29 2014 -0700
>
> Fix a typo.
>
> Signed-off-by: Warren Turkal <wt@penguintechs.org>
Thanks, I applied the patch to kbuild.git#misc. But please write a more
meaningful subject line next time (I changed it to "kbuild: Fix a typo
in documentation") and use git format-patch to generate the patch, so
that the recipient can pipe your email git git am.
Michal
prev parent reply other threads:[~2014-06-10 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <539548E7.9070908@penguintechs.org>
[not found] ` <20140609074630.GA15826@ravnborg.org>
2014-06-09 8:07 ` possible typo Warren Turkal
2014-06-10 0:29 ` Randy Dunlap
2014-06-10 12:16 ` Michal Marek [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=5396F736.4080901@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=trivial@kernel.org \
--cc=wt@penguintechs.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