From: Alejandro Colomar <alx@kernel.org>
To: Stefan Puiu <stefan.puiu@gmail.com>
Cc: Svetly Todorov <svetly.todorov@memverge.com>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
Gregory Price <gregory.price@memverge.com>,
"Huang, Ying" <ying.huang@intel.com>
Subject: Re: [PATCH v4] man2: add MPOL_WEIGHTED_INTERLEAVE documentation
Date: Tue, 19 Mar 2024 12:33:22 +0100 [thread overview]
Message-ID: <Zfl4AkhiHS_REsby@debian> (raw)
In-Reply-To: <CACKs7VAwnBuz6Lsk57i70-OgrBEz-0FuFUD_O2PPZrc3UUE4Qw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
Hi Stefan,
On Tue, Mar 19, 2024 at 12:05:08PM +0200, Stefan Puiu wrote:
> Hi Alex,
>
> On Mon, Mar 18, 2024 at 5:09 PM Alejandro Colomar <alx@kernel.org> wrote:
> > Yup. That commit is already in Linus's tree:
> >
> > alx@debian:~/src/linux/linux/master$ git describe --contains fa3bea4e1f82
> > fatal: cannot describe 'fa3bea4e1f8202d787709b7e3654eb0a99aed758'
> > alx@debian:~/src/linux/linux/master$ git describe fa3bea4e1f82
> > v6.8-rc5-108-gfa3bea4e1f82
> > alx@debian:~/src/linux/linux/master$ git log --oneline torvalds/master | grep fa3bea4e1f82
> > fa3bea4e1f82 mm/mempolicy: introduce MPOL_WEIGHTED_INTERLEAVE for weighted interleaving
>
> I think you can do a simple:
>
> $ git branch --contains fa3bea4e1f82
> * master
Ahhh, didn't know that thing! Thanks! I'm still wondering why
`git describe --contains` failed. Is it because it's in a merged branch
and it would be ambiguous with another parallel commit?
Have a lovely day!
Alex
>
> Just my 2 cents,
> Stefan.
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-03-19 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 19:50 [PATCH v4] man2: add MPOL_WEIGHTED_INTERLEAVE documentation Svetly Todorov
2024-03-16 21:06 ` Alejandro Colomar
2024-03-18 14:38 ` Svetly Todorov
2024-03-18 15:09 ` Alejandro Colomar
2024-03-19 10:05 ` Stefan Puiu
2024-03-19 11:33 ` Alejandro Colomar [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=Zfl4AkhiHS_REsby@debian \
--to=alx@kernel.org \
--cc=gregory.price@memverge.com \
--cc=linux-man@vger.kernel.org \
--cc=stefan.puiu@gmail.com \
--cc=svetly.todorov@memverge.com \
--cc=ying.huang@intel.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