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

Re: [PATCH] am: add --check option

From
Johannes Sixt <j6t@kdbg.org>
Date
Jun 3, 2019, 21:09 UTC
Message-ID
<34b269e6-0172-42a3-b7b0-f0c7751007a4@kdbg.org>
In-Reply-To
<20190603142523.3826-1-sir@cmpwn.com>
Am 03.06.19 um 16:25 schrieb Drew DeVault:
> +--check::
> +	Instead of applying the patch(es), see if they are
> +	applicable to the current working tree and/or the index
> +	file and detects errors.
I have to wonder how --check works when 'am' applies multiple patches.

When the second patch in a patch series depends on that the first patch is fully applied, what does --check do? Without the first patch applied, then a naive check of the second patch will certainly fail, doesn't it?

-- Hannes
Previous: SZEDER GáborNext: René Scharfe
Message 3 of 4 in “am: add --check option”
  1. am: add --check optionDrew DeVault, Jun 3, 2019
  2. SZEDER GáborJun 3, 2019
  3. Johannes SixtJun 3, 2019
  4. René ScharfeJun 4, 2019

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.