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

4 messages from 2009-07-13 to 2009-07-16. Participants: n179911, Jeff King, Junio C Hamano.
Thread: https://gitlist.dev/t/20101

## n179911, 2009-07-13 20:53

Subject: How to ignore space when using 'git send-email' command
Message-ID: <3b9893450907131353o77102b8cx6c8944f6cc45214a@mail.gmail.com>
URL: https://gitlist.dev/e/3b9893450907131353o77102b8cx6c8944f6cc45214a%40mail.gmail.com

```
Hi,

I am using git version 1.6.1.

When i use 'git send-email' command how can I specify it to 'ignore-all-space'?
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.

I have already commit my changes to my local branch, so I can't use
'git diff' , 'git format-patch' to display the different which ignore
white spaces.

Can you please tell me how can I send-email which ignore white-spaces?

Thank you.

```

## Jeff King, 2009-07-16 10:09

Subject: Re: How to ignore space when using 'git send-email' command
Message-ID: <20090716100926.GC6742@coredump.intra.peff.net>
URL: https://gitlist.dev/e/20090716100926.GC6742%40coredump.intra.peff.net
In-Reply-To: <3b9893450907131353o77102b8cx6c8944f6cc45214a@mail.gmail.com>

```
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?

-Peff

```

## Junio C Hamano, 2009-07-16 20:57

Subject: Re: How to ignore space when using 'git send-email' command
Message-ID: <7v4otc8hy8.fsf@alter.siamese.dyndns.org>
URL: https://gitlist.dev/e/7v4otc8hy8.fsf%40alter.siamese.dyndns.org
In-Reply-To: <20090716100926.GC6742@coredump.intra.peff.net>

```
Jeff King <peff@peff.net> writes:

> 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.

```

## Jeff King, 2009-07-16 21:00

Subject: Re: How to ignore space when using 'git send-email' command
Message-ID: <20090716210051.GA17229@coredump.intra.peff.net>
URL: https://gitlist.dev/e/20090716210051.GA17229%40coredump.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:

> >   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

```