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

Re: [PATCHv1 0/2] git-p4: work on a detached head

From
Luke Diamand <luke@diamand.org>
Date
Sep 10, 2015, 12:23 UTC
Message-ID
<CAE5ih78sVaPQ_=v5ceTZjV+iJCQOy=R_Z_trOHYUPrEMHn5zzQ@mail.gmail.com>
In-Reply-To
<CA+P7+xqTGR4EfQGmOyvB=hS5YNS1hnhddFRqdjXp+DiTSbMdRQ@mail.gmail.com>
On 10 September 2015 at 02:59, Jacob Keller <jacob.keller@gmail.com> wrote:
Show 21 quoted lines
> On Wed, Sep 9, 2015 at 6:57 PM, Jacob Keller <jacob.keller@gmail.com> wrote:
>> On Wed, Sep 9, 2015 at 5:03 AM, Lars Schneider <larsxschneider@gmail.com> wrote:
>>> I wanted to play with the patch and apply it to my source but the process is really complicated for me. I wonder if you can give me a few recommendations how to work efficiently with email patches. I don’t want to start a flame-war about what email client is “right", I am just curious how you work and what clients, scripts, or tricks you use :-)
>>>
>>> Usually I use Apple Mail. I experimented with mutt but it was not dramatically more convenient.
>>>
>>> Thanks,
>>> Lars
>>
>> Generally, any client which lets you save patches as mbox format. Then
>> you can feed the file via git-am
>>
>> I don't know what clients make this easy. I normally use Evolution,
>> which has as "save as mbox" option. It's possible Apple Mail does too.
>>
>> Regards,
>> Jake
>
> For the record, you can use "show original" from GMail, and save that
> file as well, I believe. I don't know about Apple Mail specifically,
> however.

I also don't use Apple Mail, but it must surely have a way to get the original email text. Save that and then do:

$ git am /path/to/saved-file
At least, that's what I do.
Luke
Previous: Jacob Keller
Message 12 of 12 in “[PATCHv1 0/2] git-p4: work on a detached head”
  1. Luke DiamandSep 5, 2015
  2. 1/2 git-p4: add failing test for submit from detached headLuke Diamand, Sep 5, 2015
  3. 2/2 git-p4: work with a detached headLuke Diamand, Sep 5, 2015
  4. Junio C HamanoSep 9, 2015
  5. Luke DiamandSep 10, 2015
  6. Junio C HamanoSep 10, 2015
  7. Junio C HamanoOct 28, 2015
  8. Luke DiamandOct 28, 2015
  9. Lars SchneiderSep 9, 2015
  10. Jacob KellerSep 10, 2015
  11. Jacob KellerSep 10, 2015
  12. Luke DiamandSep 10, 2015

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.