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

Re: [StGit PATCH] Tutorial: Importing patches

From
CMCatalin Marinas <catalin.marinas@gmail.com>
Date
Oct 28, 2008, 22:09 UTC
Message-ID
<b0943d9e0810281509r109ee2dby51ee13a250700012@mail.gmail.com>
In-Reply-To
<20081028204223.9539.89315.stgit@yoghurt>
Hi Karl,
Thanks for the patch.
2008/10/28 Karl Hasselström <kha@treskal.com>:
Show 9 quoted lines
> +Importing a patch from an e-mail is simple too:
> +
> +  $ stg import --mail my-mail
> +
> +The e-mail should be in standard Git mail format (which is what e.g.
> +stglink:mail[] produces) -- that is, with the patch in-line in the
> +mail, not attached. The authorship info is taken from the mail
> +headers, and the commit message is read from the 'Subject:' line and
> +the mail body.

It actually supports importing diffs from attachments as well as long as they are text/plain (the description is expected in the mail body). Anyway, I think we don't have to mention this in the tutorial as most people would use the Git mail format anyway.

-- 
Catalin
Previous: Karl HasselströmNext: Karl Hasselström
Message 2 of 3 in “Tutorial: Importing patches”
  1. Tutorial: Importing patchesKarl Hasselström, Oct 28, 2008
  2. Catalin MarinasOct 28, 2008
  3. Karl HasselströmOct 29, 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.