From: Keith Seitz <keiths@redhat.com>
To: bunsen@sourceware.org
Subject: Re: [PATCH] r-dejagnu-diff-logs: fix patched-unpatched typo
Date: Mon, 22 Aug 2022 09:10:15 -0700 [thread overview]
Message-ID: <95443b0d-91f0-4f81-8c92-72c2c369a166@redhat.com> (raw)
In-Reply-To: <20220815162847.1951605-1-keiths@redhat.com>
On 8/15/22 09:28, Keith Seitz via Bunsen wrote:
> There is a little typo in get_commits() which could (or will) cause the
> user some confusion. The unpatched and patched commits are reversed
> because of a typo!
I've pushed this patch.
Keith
prev parent reply other threads:[~2022-08-22 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 16:28 Keith Seitz
2022-08-22 16:10 ` Keith Seitz [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=95443b0d-91f0-4f81-8c92-72c2c369a166@redhat.com \
--to=keiths@redhat.com \
--cc=bunsen@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).