From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the userns tree
Date: Wed, 6 Feb 2019 10:04:54 +1100 [thread overview]
Message-ID: <20190206100454.7a5066cb@canb.auug.org.au> (raw)
In-Reply-To: <87bm3pzzz3.fsf@xmission.com>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
Hi Eric,
On Tue, 05 Feb 2019 15:29:04 -0600 ebiederm@xmission.com (Eric W. Biederman) wrote:
>
> The SHA1 tag does exist and I have another tag:
> History Tree: https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git
> That lists the tree it actually came from.
Ah, tricky.
> That is the best way I can see to handle bugs that predate v2.6.12 that
> Linus first put into git.
>
> Would it make sense to graft you tree that you check for the existence
> of bad sha1s to Thomas's import of the bk tree into git?
I can just get a copy of that tree and check for things in there as
well, I guess. Though it shouldn't come up much (I hope :-))
> Is there a better way to refer to old commits that I haven't seen?
Not that I am aware of and I guess it is as good as any.
Thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-02-05 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 20:33 linux-next: Fixes tag needs some work in the userns tree Stephen Rothwell
2019-02-05 21:29 ` Eric W. Biederman
2019-02-05 23:04 ` Stephen Rothwell [this message]
2020-04-21 1:22 Stephen Rothwell
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=20190206100454.7a5066cb@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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 NNTP newsgroup(s).