From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH 1/2] gdb: remove redundant rm in local-maintainer-clean
Date: Thu, 20 Aug 2026 14:07:34 -0700 [thread overview]
Message-ID: <20260820140734.394d54c6@f44-mesa-1> (raw)
In-Reply-To: <20260820182026.745719-1-simon.marchi@efficios.com>
On Thu, 20 Aug 2026 14:20:23 -0400
Simon Marchi <simon.marchi@efficios.com> wrote:
> The local-maintainer-clean target removes a hardcoded list of
> parser-generator output files, and then removes $(YYFILES) two lines
> below. $(YYFILES) contains the same list of files, so the first rm is
> redundant. Remove it.
LGTM.
Approved-By: Kevin Buettner <kevinb@redhat.com>
next prev parent reply other threads:[~2026-08-20 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 18:20 Simon Marchi
2026-08-20 18:20 ` [PATCH 2/2] gdb: remove stale entries from gdb/.gitignore Simon Marchi
2026-08-20 21:08 ` Kevin Buettner
2026-08-20 21:07 ` Kevin Buettner [this message]
2026-08-20 21:50 ` [PATCH 1/2] gdb: remove redundant rm in local-maintainer-clean Simon Marchi
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=20260820140734.394d54c6@f44-mesa-1 \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.com \
/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