[p4] I line ending proposal
william_ivey at bmc.com
Fri Aug 17 09:09:33 PDT 2007
> One other thing - with content triggers you can of course
> check for wrong line-endings and refuse submissions.
Aside from possible performance issues, the problem there is
simlar to using an external tool - maintaining something
outside of Perforce to solve the problem. In this case,
the trigger might have to have access to some kind of
database similar to the typemap table where it could look
up what each file was supposed to be. (It could, of course,
skip non-text files.)
Attributes could provide that information, but isn't there
a persistence problem - some operations could clear them?
Or am I behind the curve on this?
From: Robert Cowham [mailto:robert at vaccaperna.co.uk]
Sent: Friday, August 17, 2007 7:48 AM
One other thing - with content triggers you can of course check for
line-endings and refuse submissions.
The obvious drawback is performance, but if you restrict the trigger to
certain files rather than all, that would probably be fine...
Perforce also already has the possibility to add attributes to files,
it is somewhat undocumented, so it would be nice if we could standardise
a "line-ending" attribute which was then acted on by syncs etc
everyone would need to use updated clients).
More information about the perforce-user