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

Re: [PATCH] git-send-email: use ! to indicate relative path to command

From
Gregory Anders <greg@gpanders.com>
Date
May 11, 2021, 19:03 UTC
Message-ID
<YJrVBA4HP0HEqRLD@gpanders.com>
In-Reply-To
<YJrTlXzuuMoxeJay@coredump.intra.peff.net>

I also noticed this after some quick testing and just sent a v2 right before seeing your reply.

Your (untested) implementation seems much cleaner than mine, and I'm happy to give that a try. Question: is it okay that we pass just a raw command name to exec instead of a full path? That is, is there any reason we need to first find the command in PATH *and then* pass it to exec (which is what my v2 implementation does)?

Previous: Jeff KingNext: Jeff King
Message 3 of 4 in “git-send-email: use ! to indicate relative path to command”
  1. git-send-email: use ! to indicate relative path to commandGregory Anders, May 11, 2021
  2. Jeff KingMay 11, 2021
  3. Gregory AndersMay 11, 2021
  4. Jeff KingMay 11, 2021

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.