Re: committing updated po files

[Tino Meinen <a t meinen chello nl>]

> > 4) In case not commiting same changes by translators before someone will 
> >    commit changes added by update-po target translator only must merge 
> >    own/not commited yet changes using msgmerge command from 
> >    #<lang>.po.<rel> file created by cvs client and without loosing single 
> >    line can continue tranalation work.
> 
> It's you who shouldn't touch other people's work without permission in
> the first place.
> 
> If you feel otherwise, or feel that it's so simple to undo your changes
> if needed so there was no real harm in committing those changes in the
> first place, then you have totally misunderstood the rules of behavior
> for any write access repository, and should not be allowed write access
> to any repository within lightyears of range.
I'm surprised you could even make sense of what Tomasz said in comment 4, Cristian.
I've read that comment several times and I still don't have a clue what
he said or means.
I know we should not judge people here on their knowledge and
understanding of the English language but Tomasz' rendition of it is on
the more extreme side of incomprehensible.

Anyway, I completely agree on your assesment and handling of this issue,
Christian.
Thank you very much.

These kind of things are always bad when they happen. Collaborative
projects  (like the GTP) where people are sometimes granted more
permissions than they strictly need, are always susceptible to incidents
like these. 
But we're fortunate that they don't happen too often.
So I don't think we need to consider changing our policy on this one
incident. (not that you suggested anything like that, just thinking out
loud.)

Regards
Tino Meinen