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

Re: [FEATURE REQUEST] - extend git request-pull to send email

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 3, 2011, 22:59 UTC
Message-ID
<7vpqr8zpux.fsf@alter.siamese.dyndns.org>
In-Reply-To
<AANLkTi=kXJF_rYGMyh1gj49J7fh-ZxD7Bo8o_ELHb-2M@mail.gmail.com>
Eugene Sajine <euguess@gmail.com> writes:
> Specifying the "--to user@server.com" could be a trigger for this functionality.
> All additional parameters from git send-mail should be available.
>
> What do you think?
Horrible ;-).

If this were not about request-pull but some other command that produces a summary of recent changes you have, which you might want to distribute to people who are involved in the project (e.g. Meta/cook), it might make sense to have "generate and then e-mail" feature inside the command, because such a command needs to inspect the history and grab various kinds of information anyway, and adding "people involved" to the mix might make sense.

But you are talking about request-pull, which is by design is meant to be sent to a single recipient. If the user has to say --to user@example.com, how is it different from piping the output to "| mail to@example.com"?

Previous: Eugene SajineNext: Junio C Hamano
Message 2 of 5 in “[FEATURE REQUEST] - extend git request-pull to send email”
  1. Eugene SajineFeb 3, 2011
  2. Junio C HamanoFeb 3, 2011
  3. Junio C HamanoFeb 3, 2011
  4. Eugene SajineFeb 3, 2011
  5. Eugene SajineFeb 3, 2011

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.