On 10/20/08 17:39, Philipp Lohmann wrote:
Hi,
Jens-Heiner Rechtien wrote:
I somehow don't like tying SCM functionality to commit messages, but
that's may be just me.
And should we enforce policy (like tabs vs spaces etc) via the SCM tool?
is there another point where we could actually enforce policy ? Enforce
as in preemptive, not cooperating ? It would have the advantage that
people cannot simply forget this. OTOH code formatting has the potential
to create a holy war about nothing (namely whitespace).
Well, there is a clearcut requirement in the OOo coding style. And
whitespace is not "nothing", as it is really reducing productivity on
merges/rebases.
Personally I'd prefer this to be not a check, but an automatic on the
fly reformat - but I assume that would occasionally break a file, if the
input deviates too much (or in an unexpected way) from the expected format.
The only alternative point where this could be enforced is on the
master: After all cws are integrated, all lines that were added/updated
all reformatted. This would ensure no nonconforming new code will be
added, without creating huge diffs that every cws would have to cope
with on merge/rebase.
Have Fun, Björn
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
