Re: [PATCH v7 3/4] builtin/stash: provide a way to export stashes to a ref

From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date: Jun 11, 2025, 11:31 UTC
Message-ID: <8498845e-3580-4f37-b60a-8f32c5d41f15@app.fastmail.com>
In-Reply-To: <20250601223225.464076-4-sandals@crustytoothpaste.net>

I only bring up this minor point since I read that there will be a next version anyway.

On Mon, Jun 2, 2025, at 00:32, brian m. carlson wrote:

Show 10 quoted lines

> +--print::
> +	This option is only valid for `export`.
> ++
> +Create the chain of commits representing the exported stashes without
> +storing it anywhere in the ref namespace and print the object ID to
> +standard output.  This is designed for scripts.
> +
> +--to-ref::
> +	This option is only valid for `export`.
> ++

The existing options say “for [the] `<cmd>` command”. So that’s a minor deviation from the convention.

-- 
Kristoffer Haugsbakk

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