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

Re: [GSoC PATCH v2] revision: remove log_reencode field from rev_info

From
D. Ben Knoble <ben.knoble@gmail.com>
Date
Apr 25, 2025, 12:51 UTC
Message-ID
<CALnO6CBw0asD2a1iK5UCDX4KXdr1+ua757nt6kEH9fdED2Apvw@mail.gmail.com>
In-Reply-To
<xmqqcyd33kba.fsf@gitster.g>
On Tue, Apr 22, 2025 at 6:26 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 11 quoted lines
>
> Lucas Seiki Oshiro <lucasseikioshiro@gmail.com> writes:
>
> > Remove the log_reencode field from struct rev-info, as it is not used.
> > This field was introduced in 52883fb, but it hasn't been used since its
> > introduction.
>
> "52883fbd (Teach log family --encoding, 2006-12-25)" is how you
> would refer to existing commit in the history.  I'll tweak that part
> of the proposed log message before applying so there is no need to
> resend.
With the usual "git show -s --format=reference", in case a reader didn't know :)
-- 
D. Ben Knoble
Previous: Junio C Hamano
Message 3 of 3 in “revision: remove log_reencode field from rev_info”
  1. revision: remove log_reencode field from rev_infoLucas Seiki Oshiro, Apr 22, 2025
  2. Junio C HamanoApr 22, 2025
  3. D. Ben KnobleApr 25, 2025

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.