git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Beat Bolli <dev+git@drbeat.li>,  git@vger.kernel.org
Subject: Re: [PATCH] unicode: update the width tables to Unicode 16
Date: Mon, 30 Sep 2024 11:12:32 -0700	[thread overview]
Message-ID: <xmqq34lh80z3.fsf@gitster.g> (raw)
In-Reply-To: <43570a02-3c99-1d07-4403-3e95c6e6720a@gmx.de> (Johannes Schindelin's message of "Sun, 29 Sep 2024 20:58:45 +0200 (CEST)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> Oh, but I obviously was not suggesting as crude a thing as to scrape it
> unconditionally, and certainly not daily. No, I was thinking about
> something checking the `Last-Modified:` header and only acting upon
> updated Unicode definitions, and checking for updates only on a weekly
> basis. Something along these lines:
> ...
> Sadly, to update the repository variable, we cannot use `permissions:`
> because the workflow syntax does not offer the `variables` scope.
> Therefore a Personal Access Token would need to be stored as a repository
> secret. I used a fine-grained token in my tests whose sope was
> Repository > Variables: read-write.

And it can make a patch and send it to the list and get reviewed the
usual way.  It is a bit curious whose Sob should be on such a patch,
but we can work out the details, if we were seriously to automate
it.  It all seems workable.

You may have already noticed, but I am lazy and tolerate manual
tasks if they do not come more often than once per quarter ;-)

Thanks.

      reply	other threads:[~2024-09-30 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 20:40 [PATCH] unicode: update the width tables to Unicode 16 Beat Bolli
2024-09-17 12:37 ` Johannes Schindelin
2024-09-17 21:54   ` Junio C Hamano
2024-09-29 18:58     ` Johannes Schindelin
2024-09-30 18:12       ` Junio C Hamano [this message]

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=xmqq34lh80z3.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=dev+git@drbeat.li \
    --cc=git@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;
as well as URLs for NNTP newsgroup(s).