Re: [RFC PATCH v4 3/3] t0014: Introduce alias testing suite

From: Eric Sunshine <sunshine@sunshineco.com>
Date: Sep 16, 2018, 07:21 UTC
Message-ID: <CAPig+cT7+Rcv-xVxUCYy7LV6+bNEWJgN4qONLaYsikfZN40YMA@mail.gmail.com>
In-Reply-To: <bd63006e-18a7-1c41-252c-cf47a65ba7cb@gmx.de>

On Fri, Sep 14, 2018 at 7:12 PM Tim Schumacher <timschumi@gmx.de> wrote:

> This is the first multi-patch series that I submitted, so I'm unsure if I
> should send the updated patch only or if I should send the complete series
> again as v5. Any pointers to what the correct procedure for this case is would
> be appreciated.

Re-send the entire series as v5. That makes it easier on reviewers (who don't need to go searching through the mailing list archive to get a full picture) and reduces Junio's workload since it's usually easier for him to re-queue a series wholesale than having to slice-and-dice some replacement patches into what was already queued.

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