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
Junio C Hamano <gitster@pobox.com>
Date
Jul 16, 2009, 20:57 UTC
Message-ID
<7v4otc8hy8.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20090716100926.GC6742@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 25 quoted lines
> On Mon, Jul 13, 2009 at 01:53:11PM -0700, n179911 wrote:
>
>> When i use 'git send-email' command how can I specify it to
>> 'ignore-all-space'?
>
> Have you tried:
>
>   git send-email --ignore-all-space origin
>
> ?
>
>> I see there is an 'ignore-all-space' option in 'git diff' and 'git
>> format-patch', but there is not such option for git send-email.
>
> There are two ways of running send-email:
>
>   1. format-patch your patches into a file or directory, and then
>      send-email on it. In this case, you need to --ignore-all-space when
>      doing the format-patch, which is what is generating the patches.
>
>   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.

Previous: Jeff KingNext: Jeff King
Message 3 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.