All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/remove-stale-files: clean up stale lib/test_fortify.log
Date: Thu, 8 Aug 2024 11:01:33 -0700	[thread overview]
Message-ID: <202408081101.93071829AA@keescook> (raw)
In-Reply-To: <20240808144328.807649-1-masahiroy@kernel.org>

On Thu, Aug 08, 2024 at 11:42:36PM +0900, Masahiro Yamada wrote:
> Commit 6eeccc5361e8 ("fortify: refactor test_fortify Makefile to fix some
> build problems") moved test_fortify.log from lib/ to lib/test_fortify/.
> 
> If lib/test_fortify.log from previous builds remains, Git will show it as
> an untracked file. Let's clean it up.
> 
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
> 
> Kees,
> Please apply this to your tree.

Ah, thanks! I didn't know about this script.

> Or, if you can modify your branch, please squash this to 6eeccc5361e8

Yes; I've squashed it now.

-Kees

> 
>  scripts/remove-stale-files | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/scripts/remove-stale-files b/scripts/remove-stale-files
> index f38d26b78c2a..8fc55a749ccc 100755
> --- a/scripts/remove-stale-files
> +++ b/scripts/remove-stale-files
> @@ -21,3 +21,5 @@ set -e
>  # then will be really dead and removed from the code base entirely.
>  
>  rm -f *.spec
> +
> +rm -f lib/test_fortify.log
> -- 
> 2.43.0
> 

-- 
Kees Cook

      reply	other threads:[~2024-08-08 18:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08 14:42 [PATCH] scripts/remove-stale-files: clean up stale lib/test_fortify.log Masahiro Yamada
2024-08-08 18:01 ` Kees Cook [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=202408081101.93071829AA@keescook \
    --to=kees@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.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 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.