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

Re: sg/commit-graph-cleanups (was Re: What's cooking in git.git (Jul 2020, #01; Mon, 6))

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 7, 2020, 18:12 UTC
Message-ID
<xmqqa70b5h3w.fsf@gitster.c.googlers.com>
In-Reply-To
<20200707172123.GD11341@szeder.dev>
SZEDER Gábor <szeder.dev@gmail.com> writes:
Show 15 quoted lines
> On Tue, Jul 07, 2020 at 09:45:21AM -0700, Junio C Hamano wrote:
>> Derrick Stolee <stolee@gmail.com> writes:
>> 
>> >> Oops, I am not sure what happened here.  There I thought were issues
>> >> pointed out at least on the latter series but was I hallucinating?
>> >
>> > I believe I have resolved all the open comments in both series.
>> 
>> OK, then I do not have to be worried.
>> 
>> Let's merge it down before -rc0.
>
> I think it was merged to next too soon.  I haven't even done with
> reporting all the issues that were already in v2.27.0, let alone
> looking through these followup series...

Oh, so what's your preference? Reverting all the commit-graph stuff that is not in 2.26 may be tempting but is not practically feasible this late in the cycle. It sounded like Derrick was OK to leave them in 'next', and I am fine with keeping them out of the upcoming release.

Previous: SZEDER GáborNext: SZEDER Gábor
Message 9 of 15 in “What's cooking in git.git (Jul 2020, #01; Mon, 6)”
  1. Junio C HamanoJul 7, 2020
  2. sg/commit-graph-cleanups (was Re: What's cooking in git.git (Jul 2020, #01; Mon, 6))Derrick Stolee, Jul 7, 2020
  3. Junio C HamanoJul 7, 2020
  4. Junio C HamanoJul 7, 2020
  5. Derrick StoleeJul 7, 2020
  6. Junio C HamanoJul 7, 2020
  7. Taylor BlauJul 7, 2020
  8. SZEDER GáborJul 7, 2020
  9. Junio C HamanoJul 7, 2020
  10. SZEDER GáborJul 10, 2020
  11. Junio C HamanoJul 10, 2020
  12. mr/bisect-in-c-2, was Re: What's cooking in git.git (Jul 2020, #01; Mon, 6)Johannes Schindelin, Jul 8, 2020
  13. Junio C HamanoJul 8, 2020
  14. Junio C HamanoJul 8, 2020
  15. Johannes SchindelinJul 9, 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.