From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH] embed git head hash as /dev/head
Date: Fri, 10 Jun 2022 10:07:11 -0400 [thread overview]
Message-ID: <546AB7A189C97E6865B97D7342EB6B66@eigenstate.org> (raw)
In-Reply-To: <e606daf1-d5ef-e497-9fab-4ff88472b999@posixcafe.org>
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.
usually, my kernels have some uncommitted local patches,
and are sometimes built outside of /sys/src
also, it feels overfit to git.
next prev parent reply other threads:[~2022-06-10 14:08 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 [this message]
2022-06-10 16:03 ` Jacob Moody
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=546AB7A189C97E6865B97D7342EB6B66@eigenstate.org \
--to=ori@eigenstate.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).