[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn blame and code reformatting

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2006-01-30 21:44:05 CET

On Mon, 30 Jan 2006, John Peacock wrote:

> twall wrote:
> > Given an "ignore-X" feature, does it make sense to hard-code it to whitespace or
> > could it easily be extended to be any regular expression? I'm thinking of some
> > files like this:
> >
> > <file path="xyzzy" modified="12pm EST"/>
> > <file path="xyzzy" modified="5pm GMT"/>
> >
> > Where I want to effectively do 's/modified=".*"/modified=""/' prior to the diff.
> Is it really so hard to ignore the one line that the above should
> display for each file so affected? Subversion does not currently
> require _any_ regex engine (the current code has a very limited '*'
> matching algorithm). I don't think this use-case is important enough to
> justify pulling in a cross-platform regex engine (which is really a very
> specialize state machine in its own language), though libpcre is very
> fine (and builds on Windows, FWIW).
People have asked for it for ignore patterns. I guess we sometimes will
have to depend on such a thing.

> One thing I glossed over is that although GNU's diff supports
> --ignore-space-change and --ignore-all-space, it does so from strictly a
> Latin-1 understanding of whitespace (tab, vtab, and space, I believe).
> Subversion is Unicode internally, so there is a much fatter target (does
> Subversion even support the Unicode Property Lists?). There was a
> certain amount of handwaving involved in my proposal... ;-)
Nope. We only assume files use an encoding equal to ASCII for the first
128 characters or so; we support only the ASCII line endings.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 30 21:45:06 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.