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

Re: What's cooking in git.git (Nov 2024, #02; Fri, 1)

From
Bence Ferdinandy <bence@ferdinandy.com>
Date
Nov 9, 2024, 08:51 UTC
Message-ID
<D5HIPT1E30HA.8F3CRTZH9XIR@ferdinandy.com>
In-Reply-To
<xmqqcyj9rz6a.fsf@gitster.g>
On Wed Nov 06, 2024 at 01:19, Junio C Hamano <gitster@pobox.com> wrote:
Show 20 quoted lines
> The "manual" to run the project on the maintainer side has this:
>
>    - If a topic that was picked up to 'seen' becomes and stays
>      inactive for 3 calendar weeks without having seen a clear
>      consensus that it is good enough to be moved to 'next', the
>      topic may be discarded from 'seen'.  Interested parties are
>      still free to revive the topic.  For the purpose of this
>      guideline, the definition of being "inactive" is that nobody
>      has discussed the topic, no new iteration of the topic was
>      posted, and no responses to the review comments were given.
>
> If the topic has been updated large-ish-ly since the previous
> rounds, it may deserve a fresh review, or the reviewers of the
> previous rounds may find it sufficient that they judge based on the
> change since the previous round (assuming that the earlier reviews
> did a good job of hunting problems in the previous rounds).  I do
> not offhand know who read the topic and how big a course-change the
> topic took during my absense, so hopefully somebody who is more
> familiar with the latest round can chime in before I dig the topic
> out from the bottom of my pile of backlog.

Thanks for the info, I'll wait then or maybe write a followup on the patch's thread sometime next week, where the previous reviewers are already CC-d.

Thanks, Bence

Previous: Junio C Hamano
Message 7 of 7 in “What's cooking in git.git (Nov 2024, #02; Fri, 1)”
  1. Junio C HamanoNov 4, 2024
  2. Taylor BlauNov 4, 2024
  3. Junio C HamanoNov 4, 2024
  4. Derrick StoleeNov 5, 2024
  5. Bence FerdinandyNov 5, 2024
  6. Junio C HamanoNov 6, 2024
  7. Bence FerdinandyNov 9, 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.