From: Keith Seitz <keiths@redhat.com>
To: bunsen@sourceware.org
Subject: Re: [PATCH] Add r-dejagnu-diff-logs to bin_SCRIPTS
Date: Mon, 15 Aug 2022 07:40:55 -0700 [thread overview]
Message-ID: <4e081be6-6951-ec9d-ba01-1bde5a30c8b3@redhat.com> (raw)
In-Reply-To: <20220801164801.361357-1-keiths@redhat.com>
Ping?
On 8/1/22 09:48, Keith Seitz via Bunsen wrote:
> When I committed this patch, I failed to do this, and the script was not being
> installed.
> ---
> bin/Makefile.am | 2 +-
> bin/Makefile.in | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/bin/Makefile.am b/bin/Makefile.am
> index 8ad6b1f..5c9e3b5 100644
> --- a/bin/Makefile.am
> +++ b/bin/Makefile.am
> @@ -5,6 +5,6 @@ bin_SCRIPTS = g-dejagnu-cluster-entropy g-testrun-clusterfinder \
> i-glibc-summarizer \
> pipeline \
> t-sourceware-mails-import t-upload-git-push \
> - r-find-testruns r-diff-testruns r-show-testrun r-httpd-browse r-dejagnu-summary
> + r-find-testruns r-diff-testruns r-show-testrun r-httpd-browse r-dejagnu-summary r-dejagnu-diff-logs
>
> EXTRA_DIST = $(bin_SCRIPTS)
> diff --git a/bin/Makefile.in b/bin/Makefile.in
> index bbd2459..9544927 100644
> --- a/bin/Makefile.in
> +++ b/bin/Makefile.in
> @@ -243,7 +243,7 @@ bin_SCRIPTS = g-dejagnu-cluster-entropy g-testrun-clusterfinder \
> i-glibc-summarizer \
> pipeline \
> t-sourceware-mails-import t-upload-git-push \
> - r-find-testruns r-diff-testruns r-show-testrun r-httpd-browse r-dejagnu-summary
> + r-find-testruns r-diff-testruns r-show-testrun r-httpd-browse r-dejagnu-summary r-dejagnu-diff-logs
>
> EXTRA_DIST = $(bin_SCRIPTS)
> all: all-am
next prev parent reply other threads:[~2022-08-15 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 16:48 Keith Seitz
2022-08-15 14:40 ` Keith Seitz [this message]
2022-08-15 14:42 ` Keith Seitz
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=4e081be6-6951-ec9d-ba01-1bde5a30c8b3@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).