public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: new version of the rename_rev.pl script
Date: Thu, 29 Oct 2015 15:59:08 +0530	[thread overview]
Message-ID: <20151029102908.GA1331@sudip-pc> (raw)
In-Reply-To: <20151029092210.GG7289@mwanda>

On Thu, Oct 29, 2015 at 12:22:10PM +0300, Dan Carpenter wrote:
> rename_rev.pl is a script to strip away the mechanical changes that we
> often see in staging patches and leave just the interesting changes for
> manual review.

Thanks Dan. This CamelCase feature will be a life saver. I hope you
remember few days back we had a looooong series of renames, though that
was not CamelCase. But i just checked and your script works in normal
variable rename also (state => cur_state).

Thanks again for sharing.

regards
sudip

      reply	other threads:[~2015-10-29 10:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29  9:22 new version of the rename_rev.pl script Dan Carpenter
2015-10-29 10:29 ` Sudip Mukherjee [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=20151029102908.GA1331@sudip-pc \
    --to=sudipm.mukherjee@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@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