From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Willy Tarreau <w@1wt.eu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>,
Nick Desaulniers <ndesaulniers@google.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Overly aggressive .gitignore file?
Date: Wed, 5 Jul 2023 09:51:22 -0400 [thread overview]
Message-ID: <20230705-91-oregon-tribune-77e07e@meerkat> (raw)
In-Reply-To: <20230705004129.GI1178919@mit.edu>
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
next prev parent reply other threads:[~2023-07-05 13:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 19:49 Linus Torvalds
2023-07-04 21:15 ` Willy Tarreau
2023-07-04 21:20 ` Linus Torvalds
2023-07-04 21:34 ` Willy Tarreau
2023-07-04 21:44 ` Linus Torvalds
2023-07-04 21:56 ` Willy Tarreau
2023-07-04 22:14 ` Linus Torvalds
2023-07-04 22:27 ` Willy Tarreau
2023-07-05 0:41 ` Theodore Ts'o
2023-07-05 13:51 ` Konstantin Ryabitsev [this message]
2023-07-07 18:51 ` Nick Desaulniers
2023-07-07 19:11 ` Linus Torvalds
2023-07-05 8:31 ` Bernd Petrovitsch
2023-07-05 1:59 ` Masahiro Yamada
2023-07-05 15:34 ` Theodore Ts'o
2023-07-05 16:28 ` Masahiro Yamada
2023-07-05 3:45 ` Nicolas Schier
2023-07-05 5:04 ` Masahiro Yamada
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=20230705-91-oregon-tribune-77e07e@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®