git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mark Ryden" <markryde@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: white spaces in a patch
Date: Wed, 17 Dec 2008 14:10:54 +0200	[thread overview]
Message-ID: <dac45060812170410h20e710b0ted10d46b9b96ac9d@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0812171307460.28560@intel-tinevez-2-302>

Hello,
Thanks!

"git diff --check" indeed tells about trailing whitespace
Mark

On Wed, Dec 17, 2008 at 2:08 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Tue, 16 Dec 2008, Junio C Hamano wrote:
>
>> "Mark Ryden" <markryde@gmail.com> writes:
>>
>> > 2) Is there a way to get some messages about that there are white
>> >    spaces when creating a git patch?
>>
>> Doesn't "git diff" highlight whitespace errors?  That way, you can catch
>> errors before you make a commit that has them.
>
> Not to mention "git diff --check", which should catch them, too.
>
> Ciao,
> Dscho
>
>

      reply	other threads:[~2008-12-17 12:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17  7:31 white spaces in a patch Mark Ryden
2008-12-17  7:34 ` Junio C Hamano
2008-12-17 11:44   ` Mark Ryden
2008-12-17 12:13     ` Sverre Rabbelier
2008-12-17 12:13       ` Mark Ryden
2008-12-17 12:15         ` Thomas Jarosch
2008-12-17 12:22           ` Mark Ryden
2008-12-17 20:02             ` Matthieu Moy
2008-12-17 12:22           ` Jeff King
2008-12-17 12:16         ` Sverre Rabbelier
2008-12-17 12:08   ` Johannes Schindelin
2008-12-17 12:10     ` Mark Ryden [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dac45060812170410h20e710b0ted10d46b9b96ac9d@mail.gmail.com \
    --to=markryde@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).