From: ebiederm@xmission.com (Eric W. Biederman)
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Tue, 05 Feb 2019 15:29:04 -0600 [thread overview]
Message-ID: <87bm3pzzz3.fsf@xmission.com> (raw)
In-Reply-To: <20190206073330.6e266351@canb.auug.org.au> (Stephen Rothwell's message of "Wed, 6 Feb 2019 07:33:30 +1100")
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi Eric,
>
> In commit
>
> a692933a8769 ("signal: Always attempt to allocate siginfo for SIGSTOP")
>
> Fixes tag
>
> Fixes: 6dfc88977e42 ("[PATCH] shared thread signals")
>
> has these problem(s):
>
> - Target SHA1 does not exist
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.
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?
Is there a better way to refer to old commits that I haven't seen?
Eric
next prev parent reply other threads:[~2019-02-05 21:29 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 [this message]
2019-02-05 23:04 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
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=87bm3pzzz3.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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