From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] typo in commit message
Date: Mon, 10 Oct 2016 08:43:49 -0400 (EDT) [thread overview]
Message-ID: <1069384844.2648.1476103429058.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20161010123034.GA1478@rei>
----- Original Message -----
> From: "Cyril Hrubis" <chrubis@suse.cz>
> To: ltp@lists.linux.it
> Sent: Monday, 10 October, 2016 2:30:34 PM
> Subject: [LTP] typo in commit message
>
> 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?
I would prefer to avoid force push, specially when we don't know
how many people already cloned it.
How about we do a revert and apply fixed patch instead?
Regards,
Jan
>
> --
> Cyril Hrubis
> chrubis@suse.cz
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
>
next prev parent reply other threads:[~2016-10-10 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 12:30 [LTP] typo in commit message Cyril Hrubis
2016-10-10 12:39 ` Peter Maydell
2016-10-10 12:43 ` Jan Stancek [this message]
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=1069384844.2648.1476103429058.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox