[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230705-91-oregon-tribune-77e07e@meerkat>
Date: Wed, 5 Jul 2023 09:51:22 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Theodore Ts'o <tytso@....edu>
Cc: Willy Tarreau <w@....eu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Masahiro Yamada <masahiroy@...nel.org>,
Nicolas Schier <nicolas@...sle.eu>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Overly aggressive .gitignore file?
On Tue, Jul 04, 2023 at 08:41:29PM -0400, Theodore Ts'o wrote:
> For whatever it's worth, I always run "b4 am -o /tmp/m ...", so all of
> the .mbox files end up in /tmp/m. Similarly, I'll always run "git ty
> -o /tmp/e ..." so all of the thanks file end up in /tmp/e. And that
> way I inspect the b4 output files before I run "git am -s /tmp/m/..."
> or "git send-mail /tmp/e/...".
I *have* considered auto-cleanup of stale .mbx/.cover files using the same
logic we use with "b4 ty" to recognize when a series has been already applied.
I can turn this on as an experimental feature in the current master and see if
this is at all useful.
-K
Powered by blists - more mailing lists