git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Git help for kernel archeology, suppress diffs caused by CVS keyword expansion
Date: Sun, 22 Jul 2007 19:45:58 -0400	[thread overview]
Message-ID: <9e4733910707221645x21d74e70y3c43bc8c02a9d4ca@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707222238180.14781@racer.site>

On 7/22/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> As you already did, this is my attempt at a perl script...  Feel free to
> bash my Perl capabilities, or to correct it...

I don't really know Perl but Perl is probably a better language for
this. I was doing it in C.
This doesn't run on the two full kernel samples I sent you. That's the
problem I was having, I can catch 95% of the expanded keywords with my
program but I have to touch up 5% by hand. I'll stare at this and see
if I can increase my understanding of Perl.

>
> Ciao,
> Dscho
>
> -- snipsnap --
> #!/usr/bin/perl
>
> sub init_hunk {
>         $_ = $_[0];
>         $current_hunk = "";
>         $current_hunk_header = $_;
>         ($start_minus, $dummy, $start_plus, $dummy) =
>                 /^\@\@ -(\d+)(,\d+|) \+(\d+)(,\d+|) \@\@/;
>         $plus = $minus = $space = 0;
>         $skip_logs = 0;
> }
>
> sub flush_hunk {
>         if ($plus > 0 || $minus > 0) {
>                 if ($current_file ne "") {
>                         print $current_file;
>                         $current_file = "";
>                 }
>                 $minus += $space;
>                 $plus += $space;
>                 print "\@\@ -$start_minus,$minus "
>                         . "+$start_plus,$plus \@\@\n";
>                 print $current_hunk;
>         }
> }
>
> sub check_file {
>         $_ = $_[0];
>         $current_file = $_;
>         while (<>) {
>                 if (/^\@\@/) {
>                         last;
>                 }
>                 $current_file .= $_;
>         }
>
>         init_hunk $_;
>
>         # check hunks
>         while (<>) {
>                 if ($skip_logs && /^\+ *\*/) {
>                         # do nothing
>                 } elsif (/^\@\@.*/) {
>                         flush_hunk;
>                         init_hunk $_;
>                 } elsif (/^diff/) {
>                         flush_hunk;
>                         return;
>                 } elsif (/^-.*\$(Id|Revision|Author|Date).*\$/) {
>                         $key = $1;
>                         s/^-/ /;
>                         $current_hunk .= $_;
>                         $space++;
>                         $_ = <>;
>                         if (!/\+.*\$Id.*\$/) {
>                                 die "Expected some changed \$$key line: $_";
>                         }
>                         $skip_logs = 0;
>                 } elsif (/^ .*\$Log.*\$/) {
>                         $current_hunk .= $_;
>                         $space++;
>                         $skip_logs++;
>                 } elsif (/^ /) {
>                         $current_hunk .= $_;
>                         $space++;
>                         $skip_logs = 0;
>                 } elsif (/^\+/) {
>                         $current_hunk .= $_;
>                         $plus++;
>                 } elsif (/^-/) {
>                         $current_hunk .= $_;
>                         $minus++;
>                         $skip_logs = 0;
>                 } else {
>                         die "Unexpected line: $_";
>                 }
>         }
> }
>
> while (<>) {
>         if (/^diff/) {
>                 do {
>                         check_file $_;
>                 } while(/^diff/);
>         } else {
>                 printf $_;
>         }
> }
>


-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2007-07-22 23:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-22 18:48 Git help for kernel archeology, suppress diffs caused by CVS keyword expansion Jon Smirl
2007-07-22 19:00 ` Johannes Schindelin
2007-07-22 19:10   ` Jon Smirl
2007-07-22 19:15     ` Johannes Schindelin
2007-07-22 19:48       ` Jon Smirl
2007-07-22 21:39         ` Johannes Schindelin
2007-07-22 23:45           ` Jon Smirl [this message]
2007-07-22 23:50             ` Johannes Schindelin
2007-07-23  0:11               ` Jon Smirl
2007-07-23  0:37                 ` Johannes Schindelin
2007-07-23 14:44                   ` Jon Smirl
2007-07-23 15:11                     ` Simon 'corecode' Schubert
2007-07-23 20:11                     ` Johannes Schindelin
2007-07-24  0:43                       ` Jon Smirl
2007-07-24  1:06                         ` Jon Smirl
2007-07-24  1:16                         ` Johannes Schindelin
2007-07-24 10:16                           ` Jakub Narebski
2007-07-24 11:26                             ` Johannes Schindelin
2007-07-24 13:08                               ` Jon Smirl
2007-07-22 19:09 ` Linus Torvalds
2007-07-22 19:12   ` Jon Smirl
2007-07-22 19:37     ` Linus Torvalds
2007-07-22 19:17   ` David Kastrup
2007-07-22 19:47 ` Jan Engelhardt

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=9e4733910707221645x21d74e70y3c43bc8c02a9d4ca@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@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).