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

Re: Enforcing Code Style

From: Tom Browder <tom.browder_at_gmail.com>
Date: Thu, 28 Aug 2008 06:45:30 -0500

On Thu, Aug 28, 2008 at 6:37 AM, John Aldridge
<john.aldridge_at_informatix.co.uk> wrote:
> I have another use case related to this: HTML documents. The problem is that
> we have various HTML editors in use, all of which have different ideas about
> how to layout HTML. The result is that diffs & blame are pretty much
> useless. A custom diff tool might help a bit, but blame will still be a
> Apart from just living with the problem, there seem to be a few options:
> c) Implement a pre-commit hook which checks that the data is already in some
> standard format as produced by htmltidy, and rejects the commit if not.
> It would be nice, though, to be able to run htmltidy automatically as part
> of the commit process. Whilst I wouldn't want to run a pretty printer over
> (e.g.) C++ source code -- people are entitled to have their carefully
> considered code layout respected, IMO -- I think the issues are different
> with HTML where people generally don't look at the raw text even when
> editing a document.


> It would be nicest if this could be done server-side, because otherwise
> there might be problems with people using different repositories with
> different canonicalization rules, and because there are otherwise client
> configuration and deployment issues.

John, great idea, I'm on your side--I vote yes!


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-28 13:46:06 CEST

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

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