From: Frank Gevaerts <frank_at_gevaerts.be>
Date: Sat, 12 Jun 2010 22:34:31 +0200

Hi,

I've recently found out that some people consciously don't set svn
properties and keywords on files they commit, for various reasons,
including "it's not convenient with git-svn" and "they're useless".

I think that not knowing how to set them or forgetting about them is
normal and acceptable every now and then, but I don't think wilfully
ignoring our conventions about them is something we should tolerate.

While of course ideally the properties should be set in the same commit
that adds the file, setting them in a separate commit from a separate
svn checkout would (in my opinion) be a usable workaround for
deficiencies in the tools.

Opinions?

Frank

-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan

Received on 2010-06-12