From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mike Kravetz <mike.kravetz@oracle•com>
Cc: Andrew Morton <akpm@linux-foundation•org>,
Linus Torvalds <torvalds@linux-foundation•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the mm-stable tree
Date: Mon, 10 Oct 2022 12:56:24 +1100 [thread overview]
Message-ID: <20221010125624.7030e208@canb.auug.org.au> (raw)
In-Reply-To: <Y0N3/wtn3dR2h6TT@monkey>
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
Hi Mike,
On Sun, 9 Oct 2022 18:40:15 -0700 Mike Kravetz <mike.kravetz@oracle•com> wrote:
>
> For all of these, I was under the impression that the SHA1 of commits in
> Andrew's trees were not stable and could change. That is why I purposely
> did not try to add SHA1s to the tags. Perhaps that is no longer the case
> since Andrew is using git to manage patches?
I assume that once a commit is in the mm-stable branch of Andrew's tree
that the SHA1 will be fixed (except in exceptional circumstances).
Andrew?
> I see that a pull request including these commits was already sent to
> Linus. Not sure where these are in the process, or if it may be too
> late to update. Let me know if there is anything I can do.
Yeah, I saw that, and as you say, we must just have to live with these.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-10-10 1:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 8:35 linux-next: Fixes tag needs some work in the mm-stable tree Stephen Rothwell
2022-10-09 9:15 ` Stephen Rothwell
2022-10-10 1:40 ` Mike Kravetz
2022-10-10 1:56 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-09 8:38 Stephen Rothwell
2022-10-09 8:36 Stephen Rothwell
2022-10-09 8:32 Stephen Rothwell
2022-09-12 5:45 Stephen Rothwell
2022-09-12 13:05 ` Wang, Haiyue
2022-09-12 18:55 ` Andrew Morton
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=20221010125624.7030e208@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mike.kravetz@oracle$(echo .)com \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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