kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: Andy Whitcroft <apw@canonical.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: external tool to remove embedded filenames
Date: Fri, 02 Oct 2020 08:13:58 -0700	[thread overview]
Message-ID: <cc3efa9aa8955e15255807fc852a4ad3d8ab7f44.camel@perches.com> (raw)
In-Reply-To: <20201002144936.GA17987@Gentoo>

( * removing mentors, I originally meant to send that to mentees )

On Fri, 2020-10-02 at 20:19 +0530, Bhaskar Chowdhury wrote:
> On 11:47 Thu 01 Oct 2020, Joe Perches wrote:
> > It's rather unnecessary for files to contain their
> > path/filename in source code comments.
> > 
> > Here's a trivial little script that can remove
> > embedded filenames in c90 style comments from files.
> > 
> > This requires git.
[]
> > Running it on today's -next gives:
> > 
> > $ perl remove_embedded_filenames.pl
> > $ git diff --shortstat
> > 2310 files changed, 354 insertions(+), 4239 deletions(-)
> > 
> > It's also possible to give any filename or path
> > as an argument to the script
> > 
> > For instance:
> > 
> > $ perl remove_embedded_filenames.pl drivers/net

The below was an attachment, it's odd that your
mailer quoted it.

> > #!/usr/bin/perl -w
[]
> > if ($modified && !$quiet) {
> >    print <<EOT;
> > Warning: these changes may not be correct.
> > 
> > These changes should be carefully reviewed manually and not combined with
> > any functional changes.
> > 
> > Compile, build and test your changes.
> > 
> > You should understand and be responsible for all object changes.
> > 
> > Make sure you read Documentation/SubmittingPatches before sending
> > any changes to reviewers, maintainers or mailing lists.
> > EOT
> > }
> 
> Suggestion.... please take those damn EOT lines out of it

No.  What's your actual problem with it?

It's a tool and it may not be perfect.

It merely emits a single message if it removes
filenames from files.



_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      reply	other threads:[~2020-10-02 15:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1fd5f9188a14acdca703ca00301ee323de672a8d.camel@perches.com>
2020-10-01 18:47 ` external tool to remove embedded filenames Joe Perches
2020-10-02 14:49   ` Bhaskar Chowdhury
2020-10-02 15:13     ` Joe Perches [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=cc3efa9aa8955e15255807fc852a4ad3d8ab7f44.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=unixbhaskar@gmail.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).