netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: james@jchapman.plus.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 00/12] l2tp: Introduce L2TPv3 support
Date: Tue, 23 Mar 2010 11:53:44 -0700 (PDT)	[thread overview]
Message-ID: <20100323.115344.134124384.davem@davemloft.net> (raw)
In-Reply-To: <2f9409cb1003230319u799ef2e4l583f4f667ffa0169@mail.gmail.com>

From: James Chapman <james@jchapman.plus.com>
Date: Tue, 23 Mar 2010 10:19:03 +0000

> scripts/checkpatch.pl didn't pick these up. Is there a recommended way
> to find these in the future? I'm using stg to manage these patches.

GIT warns about them when you try to apply them.

I check patches using a dry run with a script that looks
something like:

#!/bin/sh
set -x
git apply --check --whitespace=error-all $1

  reply	other threads:[~2010-03-23 18:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23 10:19 [PATCH 00/12] l2tp: Introduce L2TPv3 support James Chapman
2010-03-23 18:53 ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-03-18 10:21 James Chapman
2010-03-20  6:23 ` David Miller

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=20100323.115344.134124384.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=james@jchapman.plus.com \
    --cc=netdev@vger.kernel.org \
    /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).