From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] typo in commit message
Date: Mon, 10 Oct 2016 14:30:34 +0200 [thread overview]
Message-ID: <20161010123034.GA1478@rei> (raw)
Hi!
I've did a confusing typo in commit:
https://github.com/linux-test-project/ltp/commit/ebfb34503c7928368043182a2ac7750e805c4911
There is no such thing as ppc32le of course, it should have been
ppc64le. Is everyone OK with me force pushing with the simple change in
the commit message?
--
Cyril Hrubis
chrubis@suse.cz
next reply other threads:[~2016-10-10 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 12:30 Cyril Hrubis [this message]
2016-10-10 12:39 ` [LTP] typo in commit message Peter Maydell
2016-10-10 12:43 ` Jan Stancek
2016-10-10 12:46 ` Cyril Hrubis
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=20161010123034.GA1478@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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.