Line ending translation extension
Dirkjan Ochtman
dirkjan at ochtman.nl
Mon Sep 7 08:16:27 CDT 2009
On Mon, Sep 7, 2009 at 14:13, Douglas Philips<dgou at mac.com> wrote:
> In a DVCS, policy decisions (such a line endings) can only be enforced
> by hooks running on the repos wishing to enforce those policy
> decisions. Anyone who can clone your repo, can make changes: with
> funky line ending mixings, funky mixed character encodings, tabs and
> spaces, whatever they want. That is the point of a DVCS. It seems that
> what you want is to have a set of hooks on your "we care about these"
> repos that will reject any changesets that violate your style. As an
> example, NetBeans has a number of hooks to enforce their requirements:
> http://wiki.netbeans.org/HgHowTos#section-HgHowTos-ServerHooksAbortPretxnchangegroup.somethingHookFailed
> (or: http://bit.ly/bA3d0)
>
> You can even suggest that folks who clone your repo(s) set up commit
> hooks for their local repos, so as to catch the same issues that your
> shared repos will catch. This way when they try commit locally they'll
> be warned/prohibited and can fix their stylistic violations sooner
> rather than later.
Yeah, I've made that point a zillion times, but apparently that just
won't do for the python-dev community.
Cheers,
Dirkjan
More information about the Mercurial
mailing list