git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] unicode: update the width tables to Unicode 16

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 30, 2024, 18:12 UTC
Message-ID
<xmqq34lh80z3.fsf@gitster.g>
In-Reply-To
<43570a02-3c99-1d07-4403-3e95c6e6720a@gmx.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 11 quoted lines
> 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.
Previous: Johannes Schindelin
Message 5 of 5 in “unicode: update the width tables to Unicode 16”
  1. unicode: update the width tables to Unicode 16Beat Bolli, Sep 12, 2024
  2. Johannes SchindelinSep 17, 2024
  3. Junio C HamanoSep 17, 2024
  4. Johannes SchindelinSep 29, 2024
  5. Junio C HamanoSep 30, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.