From: Kees Cook <keescook@chromium.org>
To: linux-next@vger.kernel.org
Subject: change to Next/SHA1s ?
Date: Mon, 28 Feb 2022 10:43:37 -0800 [thread overview]
Message-ID: <202202281042.733E768F@keescook> (raw)
Hi!
I was curious if it might be possible to emit the commit date along with
the tree/SHA1 map in Next/SHA1s? That would let people trivially scan
the file for relative age of trees, etc.
-Kees
--
Kees Cook
next reply other threads:[~2022-02-28 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 18:43 Kees Cook [this message]
2022-02-28 22:46 ` change to Next/SHA1s ? Stephen Rothwell
2022-02-28 23:05 ` Kees Cook
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=202202281042.733E768F@keescook \
--to=keescook@chromium.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