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

Re: [PATCH RFC] git-send-email --expand-aliases

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 24, 2009, 07:25 UTC
Message-ID
<7vfx84jsef.fsf@alter.siamese.dyndns.org>
In-Reply-To
<b8197bcb0911232312l251dfbc9va671388cfb7fe57b@mail.gmail.com>
Karl Wiberg <kha@treskal.com> writes:
> I think that sounds like a splendid idea. It would be interesting to
> see just how thin a wrapper around git send-email (and format-patch)
> stg mail could become, without sacrificing features anyone actually
> uses. The main complication could be stg mail's templates.

Why do you even need to run format-patch? If stg mail supports a good templates to prepare message files, it would be natural to keep using that to prepare message files.

Previous: Karl WibergNext: Karl Wiberg
Message 5 of 9 in “git-send-email --expand-aliases”
  1. git-send-email --expand-aliasesAlex Chiang, Nov 23, 2009
  2. Junio C HamanoNov 24, 2009
  3. Alex ChiangNov 24, 2009
  4. Karl WibergNov 24, 2009
  5. Junio C HamanoNov 24, 2009
  6. Karl WibergNov 24, 2009
  7. Catalin MarinasNov 24, 2009
  8. Alex ChiangNov 24, 2009
  9. Karl WibergNov 24, 2009

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.