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

Cover letter

From
PCPaolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Date
Jan 8, 2008, 12:52 UTC
Message-ID
<4d8e3fd30801080452g71c3d3dx39f2ec805239ef01@mail.gmail.com>

Hi all, I'm going to experiment the git-send-email command quite soon and I have a doubt that I would like to clarify.

I'm used to the following work flow:
- git branch trivial
- git checkout trivial
- work work work
- git gui to commit all the changes
- git-format-patch -n -o /home/paolo/patches
- open the MUA
- write the cover letter
- import the N patches
- send all the patches
- collect feedback
- work work work
- git rebase -i
- back to the git gui to commit all the changes line

This is working fine but since I'm going to push out a queue of patches it would be nicer to script everything with git-send-email.

I know I have to configure git in order to use the gmail's smtp server, I know how to tell git-send-email where to pick up the patches but I fail to understand how I can write a cover letter and let it be part of the patch queue.

Any hint?
Thanks in advance.
-- 
Paolo
http://paolo.ciarrocchi.googlepages.com/
Next: Gustaf Hendeby
Message 1 of 3 in “Cover letter”
  1. Paolo CiarrocchiJan 8, 2008
  2. Gustaf HendebyJan 8, 2008
  3. Paolo CiarrocchiJan 8, 2008

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.