From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kees Cook <keescook@chromium.org>
Cc: linux-next@vger.kernel.org
Subject: Re: change to Next/SHA1s ?
Date: Tue, 1 Mar 2022 09:46:44 +1100 [thread overview]
Message-ID: <20220301094644.58360917@canb.auug.org.au> (raw)
In-Reply-To: <202202281042.733E768F@keescook>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
Hi Kees,
On Mon, 28 Feb 2022 10:43:37 -0800 Kees Cook <keescook@chromium.org> wrote:
>
> 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.
Of course it is possible :-) Just wondering what the use case is? It
does make it a bit harder to read (wider lines).
while read tree sha; do
if [ "$tree" = 'Name' ] || [ "$tree" = '----' ]; then
printf '%s\t%s\n' "$tree" "$sha"
else
git log -1 --date=iso-strict-local --pretty="$tree $sha %cd" "$sha"
fi
done <Next/SHA1s
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-28 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 18:43 change to Next/SHA1s ? Kees Cook
2022-02-28 22:46 ` Stephen Rothwell [this message]
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=20220301094644.58360917@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=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