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

Re: [PATCH] reftable: technical documentation link fixes

From
Carlo Marcelo Arenas Belón <carenas@gmail.com>
Date
May 26, 2020, 23:16 UTC
Message-ID
<20200526231617.GA40564@Carlos-MBP>
In-Reply-To
<CAFQ2z_NaCGypqPD6V1k0eXWQYnCm5WE_wz+6vJURd=Cc6nHA4w@mail.gmail.com>
On Tue, May 26, 2020 at 08:53:08PM +0200, Han-Wen Nienhuys wrote:
> 
> What do I do now? Does Junio fold this in, or do I have to send an
> updated patch series?

since the issue was introduced with 27eede2922 (reftable: file format documentation, 2020-05-20) which is already in next, then Junio might just add it to the tip of either hn/reftable or hn/refs-cleanup and include it with the reroll that would come after the 2.27 release.

if you have other fixes and are planning a reroll on those branches then it might be better if you squash it in and therefore avoid both the bug and my typo in the commit message.

Carlo
Previous: Han-Wen NienhuysNext: Jonathan Nieder
Message 4 of 6 in “reftable: technical documentation link fixes”
  1. reftable: technical documentation link fixesCarlo Marcelo Arenas Belón, May 25, 2020
  2. Carlo Marcelo Arenas BelónMay 25, 2020
  3. Han-Wen NienhuysMay 26, 2020
  4. Carlo Marcelo Arenas BelónMay 26, 2020
  5. Jonathan NiederMay 27, 2020
  6. Junio C HamanoMay 27, 2020

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.