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

Re: [subversion-dev] I/O filters and scripts.

From: Jonathan S. Shapiro <shap_at_eros-os.org>
Date: 2000-06-15 14:18:58 CEST

> One major feature that I'd very much like to see in Subversion is the
> idea of input & output filters.
> Shap and Zack have already mentioned a few benefits of this (6/5,
> 6/6), e.g. line feed canonicalization and variable expansion. I
> think there is much to be gained from a more general filtering
> mechanism, though.

Hmm. I thought I *was* proposing a general mechanism. Line ends and variable
expansion are just applications of that mechanism.

> I know that some people won't want to do this at all, so I
> want to emphasize that I'm suggesting an _option_.

Yes, it's an option in the sense that a given project need not use it. No,
it's not an option in the sense that code formatting policy is a decision
made by the project administrator, not by the individual user.

Which raises a broader challenge: who controls which decisions and what
roles are involved?

The complexity associated with getting this right is part of why I want a
real programming language as part of DCMS.

Received on Sat Oct 21 14:36:05 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.