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

Re: [StGit PATCH 2/2] Pass the --in-reply-to and --no-thread options to git send-email

From
Karl Wiberg <kha@treskal.com>
Date
Jan 8, 2010, 06:43 UTC
Message-ID
<b8197bcb1001072243h24e6248er79ac5a8afb6e3782@mail.gmail.com>
In-Reply-To
<20100107160937.3226.14811.stgit@pc1117.cambridge.arm.com>
On Thu, Jan 7, 2010 at 5:09 PM, Catalin Marinas <catalin.marinas@arm.com> wrote:
> +    if options.in_reply_to:
> +        cmd.append("--in-reply-to %s" % options.in_reply_to)

Have you tested this? I'm pretty sure you need "--in-reply-to=%s", or to add the two strings separately---since as far as I can see, this command is never shell-expanded.

-- 
Karl Wiberg, kha@treskal.com
   subrabbit.wordpress.com
   www.treskal.com/kalle
Previous: Catalin MarinasNext: Catalin Marinas
Message 3 of 5 in “Rename the mail --refid and --noreply options to match Git”
  1. 1/2 Rename the mail --refid and --noreply options to match GitCatalin Marinas, Jan 7, 2010
  2. 2/2 Pass the --in-reply-to and --no-thread options to git send-emailCatalin Marinas, Jan 7, 2010
  3. Karl WibergJan 8, 2010
  4. Catalin MarinasJan 8, 2010
  5. Karl WibergJan 8, 2010

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.