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

Re: Documentation issue: git-stash examples

From
Jeff King <peff@peff.net>
Date
May 25, 2017, 21:54 UTC
Message-ID
<20170525215403.v5fzw7amicyftbgi@sigill.intra.peff.net>
In-Reply-To
<CAOJu4w-cghto=LAZKQPBDBHX=JOSbHGJiYawod+45_SzvhiuNg@mail.gmail.com>
On Fri, May 26, 2017 at 08:37:41AM +1200, Adrian Forbes wrote:
> Yep, but how do I send it back to you? As a mail attachment?

Usually you'd send it to the list, with the commit message in the body and the patch inline below, as generated by "git format-patch".

Unfortunately gmail is notorious for corrupting whitespace in message bodies. You can use git-send-email to send the mails (but you'll need to configure your gmail smtp information; see the EXAMPLE section of "git help send-email").

Alternatively, you can make a pull request to https://github.com/git/git and then send it to the list via https://submitgit.herokuapp.com/.

-Peff
Previous: Jeff King
Message 3 of 3 in “Documentation issue: git-stash examples”
  1. Adrian ForbesMay 25, 2017
  2. Jeff KingMay 25, 2017
  3. Jeff KingMay 25, 2017

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.