From: Jacob Moody <moody@mail.posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] embed git head hash as /dev/head
Date: Fri, 10 Jun 2022 10:03:10 -0600 [thread overview]
Message-ID: <d7c7389b-5e94-68d3-183e-ac368ea29544@posixcafe.org> (raw)
In-Reply-To: <546AB7A189C97E6865B97D7342EB6B66@eigenstate.org>
On 6/10/22 08:07, ori@eigenstate.org wrote:
> Quoth Jacob Moody <moody@mail.posixcafe.org>:
>> This embeds the current commit hash for HEAD
>> in to devcons as /dev/head. Thought this could be
>> handy, curious to hear what others think.
>>
>
> not a fan.
Fair enough, but I did want to talk a bit about what the
use case for this is.
>
> usually, my kernels have some uncommitted local patches,
> and are sometimes built outside of /sys/src
I am going to go out on a limb here and say that a majority of
users don't have uncommitted local patches to the kernel.
I view this mostly as something that could assist it debugging,
a lot easier to know what code someone has running in their kernel
if you know what the base commit was at least. I've run in to
a number of users that were unaware of needing to update their
kernels. This gives a concrete answer of 'how out of date is the
kernel'. But this is all fluff, just thought it might prove
useful.
> also, it feels overfit to git.
Wasn't aware we shipped with other version control software :P.
Some improvements that could be made to this:
* We could check for a local .git and use that over the one in /dist if found
* We could record the tidiness of the tree, perhaps either through a 'dity' suffix
to the hash and/or just embedding the entire code diff itself.
But I wont invest more time in to this if people don't like the
idea.
Thanks,
moody
next prev parent reply other threads:[~2022-06-10 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 7:32 Jacob Moody
2022-06-10 14:07 ` ori
2022-06-10 16:03 ` Jacob Moody [this message]
2022-06-14 17:32 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-06-14 19:37 ` Jacob Moody
2022-06-10 19:01 ` mkf9
2022-06-10 19:13 ` Jacob Moody
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=d7c7389b-5e94-68d3-183e-ac368ea29544@posixcafe.org \
--to=moody@mail.posixcafe.org \
--cc=9front@9front.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).