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

Re: How to ignore space when using 'git send-email' command

From
Jeff King <peff@peff.net>
Date
Jul 16, 2009, 21:00 UTC
Message-ID
<20090716210051.GA17229@coredump.intra.peff.net>
In-Reply-To
<7v4otc8hy8.fsf@alter.siamese.dyndns.org>
On Thu, Jul 16, 2009 at 01:57:03PM -0700, Junio C Hamano wrote:
Show 9 quoted lines
> >   2. give send-email revision arguments, which are fed to format-patch
> >      (which is what I showed above).  In this case, you can give
> >      format-patch arguments directly to send-email.
> >
> > Does that help?
> 
> That may help but it is generally a bad idea to send a patch generated
> with ignore-all-spaces and other options, as it means that the receiving
> end will get changes that not even you the sender had any chance to test.

True. You are probably better off using "rebase -i" to fix your commits, testing them, then sending in the result.

-Peff
Previous: Junio C Hamano
Message 4 of 4 in “How to ignore space when using 'git send-email' command”
  1. n179911Jul 13, 2009
  2. Jeff KingJul 16, 2009
  3. Junio C HamanoJul 16, 2009
  4. Jeff KingJul 16, 2009

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.