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

Re: What's cooking in git.git (Dec 2022, #05; Wed, 14)

From
Taylor Blau <me@ttaylorr.com>
Date
Dec 14, 2022, 19:46 UTC
Message-ID
<Y5ooJJLqPP0R2SAS@nand.local>
In-Reply-To
<xmqq7cyuw9h4.fsf@gitster.g>
On Wed, Dec 14, 2022 at 07:44:23PM +0900, Junio C Hamano wrote:
Show 19 quoted lines
> Junio C Hamano <gitster@pobox.com> writes:
>
> > In the past, I tried to re-examine all the topics in 'next' myself
> > to pick and choose the ones to be kept before rewinding and
> > rebuilding 'next' after each release, which took me a while.  This
> > time, to share the burden to expedite the process, I'll reset 'next'
> > to 'master' without any topics merged, and rely on input from list
> > participants.
> >
> > The topics that used to be in 'next' are all marked as "Will merge
> > back to 'next'", but people can tell me to give them a chance to
> > reboot their topics, instead of piling "oops, that was wrong" fixes
> > on top, while I wait for such an input for the coming days.
>
> What is involved in "re-examine to pick and choose the ones to be
> kept" was to go to the original thread (which should not be too
> hard, as Taylor has maintained the "source:" line in the report well
> during my absense) see general consensus and the reason behind the
> consensus back then still applies today.

Since it wasn't obvious to me, I figure it is worth mentioning that the effort to maintain these source lines can be done via the "amlog" notes, which are automatically filled in when applying new patches from the list via your post-applypatch hook.

The relevant parts being:
  message_id="$(...)"
  if test -n "$message_id" && head=$(git rev-parse --verify HEAD 2>/dev/null)
  then
    echo "$head $message_id" >>"$GIT_DIR"/am.log &&
    (
      GIT_NOTES_REF=refs/notes/amlog
      export GIT_NOTES_REF
      git notes add -f -m "Message-Id: $message_id" "$head"
    )
  fi

I just made sure to push `refs/notes/amlog` up when doing new push-outs. The rest (including the "source:" lines in the WC reports) was made easy by your Meta/cook script.

Thanks, Taylor

Previous: Junio C HamanoNext: Derrick Stolee
Message 3 of 21 in “What's cooking in git.git (Dec 2022, #05; Wed, 14)”
  1. Junio C HamanoDec 14, 2022
  2. Junio C HamanoDec 14, 2022
  3. Taylor BlauDec 14, 2022
  4. Derrick StoleeDec 14, 2022
  5. Junio C HamanoDec 14, 2022
  6. Jeff HostetlerDec 14, 2022
  7. Junio C HamanoDec 14, 2022
  8. Jeff HostetlerDec 14, 2022
  9. Junio C HamanoDec 15, 2022
  10. ag/merge-strategies-in-c (was: What's cooking in git.git (Dec 2022, #05; Wed, 14))Ævar Arnfjörð Bjarmason, Dec 15, 2022
  11. Phillip WoodDec 15, 2022
  12. Ævar Arnfjörð BjarmasonDec 15, 2022
  13. Phillip WoodDec 15, 2022
  14. Ævar Arnfjörð BjarmasonDec 15, 2022
  15. ab/remove--super-prefix & ab/submodule-no-abspath (was: What's cooking in git.git (Dec 2022, #05; Wed, 14))Ævar Arnfjörð Bjarmason, Dec 15, 2022
  16. js/bisect-in-c (was: What's cooking in git.git (Dec 2022, #05; Wed, 14))Ævar Arnfjörð Bjarmason, Dec 15, 2022
  17. Sean AllredDec 15, 2022
  18. Junio C HamanoDec 15, 2022
  19. Junio C HamanoDec 15, 2022
  20. ds/bundle-uri-4* (was Re: What's cooking in git.git (Dec 2022, #05; Wed, 14))Derrick Stolee, Dec 16, 2022
  21. Junio C HamanoDec 16, 2022

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.