* change to Next/SHA1s ?
@ 2022-02-28 18:43 Kees Cook
2022-02-28 22:46 ` Stephen Rothwell
0 siblings, 1 reply; 3+ messages in thread
From: Kees Cook @ 2022-02-28 18:43 UTC (permalink / raw)
To: linux-next
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: change to Next/SHA1s ?
2022-02-28 18:43 change to Next/SHA1s ? Kees Cook
@ 2022-02-28 22:46 ` Stephen Rothwell
2022-02-28 23:05 ` Kees Cook
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2022-02-28 22:46 UTC (permalink / raw)
To: Kees Cook; +Cc: linux-next
[-- 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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: change to Next/SHA1s ?
2022-02-28 22:46 ` Stephen Rothwell
@ 2022-02-28 23:05 ` Kees Cook
0 siblings, 0 replies; 3+ messages in thread
From: Kees Cook @ 2022-02-28 23:05 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next
On Tue, Mar 01, 2022 at 09:46:44AM +1100, Stephen Rothwell wrote:
> 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).
My use case is that I find myself with some frequency looking at "git
show next-YYYYMMDD" to see the trees to see what date a given tree is on
(some update frequently, some don't, etc).
> 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
Right, I can do it manually, but I was wondering if such a change would
be useful to others, or troublesome, etc. :) I can live without it, for
sure; I just thought I'd ask. :)
--
Kees Cook
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-02-28 23:05 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-28 18:43 change to Next/SHA1s ? Kees Cook
2022-02-28 22:46 ` Stephen Rothwell
2022-02-28 23:05 ` Kees Cook
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.