Re: [PATCH v3 00/21] git-p4: Various code tidy-ups

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 17, 2022, 01:34 UTC
Message-ID: <xmqqr197xi0b.fsf@gitster.g>
In-Reply-To: <20220116160550.514637-1-jholdsworth@nvidia.com>

Joel Holdsworth <jholdsworth@nvidia.com> writes:

> This third version of the patch-set is rebased on top of the next
> branch.

After other p4 topics in 'next' graduate to 'master', you'd need to rebase the series again to the updated 'master', but in the meantime, people can comment on the current patches.

I'll take the series as "for discussion only" for now.

Thanks.

cf. Documantation/SubmittingPatches::[[base-branch]]

* In the exceptional case that a new feature depends on several topics
  not in `master`, start working on `next` or `seen` privately and send
  out patches for discussion. Before the final merge, you may have to
  wait until some of the dependent topics graduate to `master`, and
  rebase your work.

$ 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.