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

Re: [PATCH] archive: document --prefix handling of absolute and parent paths

From
Jeff King <peff@peff.net>
Date
Apr 8, 2026, 17:40 UTC
Message-ID
<20260408174043.GC2850002@coredump.intra.peff.net>
In-Reply-To
<20260408160005.193621-2-pushkarkumarsingh1970@gmail.com>
On Wed, Apr 08, 2026 at 04:00:06PM +0000, Pushkar Singh wrote:
Show 8 quoted lines
>  	Prepend <prefix>/ to paths in the archive.  Can be repeated; its
>  	rightmost value is used for all tracked files.  See below which
>  	value gets used by `--add-file`.
> ++
> +The <prefix> is used as given and is not normalized. It may
> +include leading slashes or parent directory components (e.g.,
> +`../`). Some archive consumers may treat such paths as
> +potentially unsafe and adjust or warn during extraction.
Thanks, this reads fine to me.
-Peff
Previous: Pushkar Singh
Message 6 of 6 in “[RFC] archive: behavior of --prefix with absolute or parent path components”
  1. Pushkar SinghApr 7, 2026
  2. Jeff KingApr 7, 2026
  3. Junio C HamanoApr 7, 2026
  4. brian m. carlsonApr 7, 2026
  5. archive: document --prefix handling of absolute and parent pathsPushkar Singh, Apr 8, 2026
  6. Jeff KingApr 8, 2026

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.