From: Christian Brauner <brauner@kernel.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Dawid Osuchowski <linux@osuchow.ski>,
jack@suse.cz, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3] fs: Create anon_inode_getfile_fmode()
Date: Wed, 8 May 2024 13:37:49 +0200 [thread overview]
Message-ID: <20240508-geeinigt-anbruch-d41b994120ed@brauner> (raw)
In-Reply-To: <20240508004659.GM2118490@ZenIV>
On Wed, May 08, 2024 at 01:46:59AM +0100, Al Viro wrote:
> On Wed, May 08, 2024 at 01:41:06AM +0100, Al Viro wrote:
>
> > So it looks like you forgot to push vfs.misc as well...
>
> BTW, IME it's useful to have all merges either go from tips of
> named branches or from tags - easier to catch that kind of
> SNAFU when one forgets to push the topical out. You can
> easily see it in e.g. gitk.
Yes, forgot to push vfs.misc. Fixed now!
next prev parent reply other threads:[~2024-05-08 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 7:58 [PATCH v3] fs: Create anon_inode_getfile_fmode() Dawid Osuchowski
2024-04-26 16:05 ` Christian Brauner
2024-05-08 0:41 ` Al Viro
2024-05-08 0:46 ` Al Viro
2024-05-08 11:37 ` Christian Brauner [this message]
2024-05-08 1:48 ` Al Viro
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=20240508-geeinigt-anbruch-d41b994120ed@brauner \
--to=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux@osuchow.ski \
--cc=viro@zeniv.linux.org.uk \
/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).