From: Uwe Kleine-Koenig <zeisberg@informatik.uni-freiburg.de>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Randal L. Schwartz" <merlyn@stonehenge.com>,
Jon Smirl <jonsmirl@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Diffs from CVS keyword expansion
Date: Wed, 6 Dec 2006 11:05:14 +0100 [thread overview]
Message-ID: <20061206100514.GA7126@informatik.uni-freiburg.de> (raw)
In-Reply-To: <Pine.LNX.4.63.0612052048230.28348@wbgn013.biozentrum.uni-wuerzburg.de>
Hi,
Johannes Schindelin wrote:
> On Tue, 5 Dec 2006, Randal L. Schwartz wrote:
>
> > >>>>> "Uwe" == Uwe Kleine-Koenig <zeisberg@informatik.uni-freiburg.de> writes:
> >
> > Uwe> #! /bin/sh
> > Uwe> exec perl -i -p -e 's/\$(Id|Revision):.*?\$/\$$1: \$/' "$@";
> >
> > Ow. My eyes hurt from that. How about we rewrite that as a native Perl
> > script:
I don't like that either, just because it's Perl :-)
> > #!/usr/bin/perl
> > $^I = ""; # this is -i
> > while (<>) {
> > s/\$(Id|Revision):.*?\$/\$$1: \$/;
> > print;
> > }
>
> Hey, that's better! All of a sudden, I understand everything!
I'm not fluent in Perl, and didn't know $^I. Actually, that's better,
yes. (And my script is already rewritten.)
One thing I don't like about both scripts is, that the timestamp of
a file changes with that, even if there are no changes. Anyone knows
another predefined variable/trick that doesn't hurt performance (and
readability) too much?
timtowtdi
Uwe
--
Uwe Kleine-Koenig
next prev parent reply other threads:[~2006-12-06 10:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 3:56 Diffs from CVS keyword expansion Jon Smirl
2006-12-01 7:06 ` Juergen Ruehle
2006-12-01 7:44 ` Linus Torvalds
2006-12-01 15:33 ` Jon Smirl
2006-12-05 12:14 ` Uwe Kleine-Koenig
2006-12-05 19:45 ` Randal L. Schwartz
2006-12-05 19:48 ` Johannes Schindelin
2006-12-06 10:05 ` Uwe Kleine-Koenig [this message]
2006-12-06 10:08 ` Randal L. Schwartz
2006-12-05 19:55 ` Junio C Hamano
2006-12-05 20:30 ` Robin Rosenberg
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=20061206100514.GA7126@informatik.uni-freiburg.de \
--to=zeisberg@informatik.uni-freiburg.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=merlyn@stonehenge.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).