All of lore.kernel.org
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Uwe Kleine-Koenig <zeisberg@informatik.uni-freiburg.de>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Jon Smirl <jonsmirl@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Diffs from CVS keyword expansion
Date: 06 Dec 2006 02:08:35 -0800	[thread overview]
Message-ID: <86irgpl4kc.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <20061206100514.GA7126@informatik.uni-freiburg.de>

>>>>> "Uwe" == Uwe Kleine-Koenig <zeisberg@informatik.uni-freiburg.de> writes:
Uwe> One thing I don't like about both scripts is, that the timestamp of
Uwe> a file changes with that, even if there are no changes.  Anyone knows
Uwe> another predefined variable/trick that doesn't hurt performance (and
Uwe> readability) too much?

You have to do two passes, or a pass-and-a-half, and do the rename/rewrite
based on whether anything changed.

"Just a few more lines of code." :)  If it's really important, I can
be coaxed to dig it up.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.

  reply	other threads:[~2006-12-06 10:09 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
2006-12-06 10:08         ` Randal L. Schwartz [this message]
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=86irgpl4kc.fsf@blue.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jonsmirl@gmail.com \
    --cc=zeisberg@informatik.uni-freiburg.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.