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

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

From
Karl Wiberg <kha@treskal.com>
Date
Nov 24, 2009, 07:12 UTC
Message-ID
<b8197bcb0911232312l251dfbc9va671388cfb7fe57b@mail.gmail.com>
In-Reply-To
<20091124004554.GA27643@ldl.fc.hp.com>
On Tue, Nov 24, 2009 at 1:45 AM, Alex Chiang <achiang@hp.com> wrote:
Show 23 quoted lines
> * Junio C Hamano <gitster@pobox.com>:
>
> > If you are changing StGit to call git-send-email anyway, why not
> > arrange stgit to call git-send-email to send the message out
> > instead, instead of sending messages on its own?
>
> Yeah, I thought about that as I was poking around further in StGit
> to figure out how it would be calling git-send-email. ;)
>
> > I imagine the internal implementation of stg mail would work
> > something like:
> >
> >     prepare messages to send out
> >     call git-send-email and have it send them
> >
> > What am I missing?
>
> My lack of familiarity with StGit internals. ;)
>
> Your suggestion is much better. I'll take a closer look at StGit and
> see how feasible it is.
>
> Unless Catalin has strong objections?

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.

Catalin, how wedded are you to those? ;-)
-- 
Karl Wiberg, kha@treskal.com
   subrabbit.wordpress.com
   www.treskal.com/kalle
Previous: Alex ChiangNext: Junio C Hamano
Message 4 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.