Paul Koning wrote on Sat, 28 Mar 2009 at 10:48 -0400:
> > I have not tested to verify this problem. But I agree Subversion
> > should prevent it. Until it does, you can prevent it by writing a pre-
> > commit hook which tests the svn:ignore property (and possibly
> > svn:externals and others). If you want to correct the problem in your
> > existing revisions and can tolerate a dump and load cycle,
> > svndumptool should be able to help you.
>
> I don't think that's the right approach.
>
> If Subversion starts to enforce a restriction that it didn't enforce in
> an earlier version, it's the responsibility of Subversion -- not of the
> admin -- to provide backwards compatibility. Preferably it should
> accept the older, less restricted, data. Failing that, it should
> provide a conversion process. Telling admins they have to construct
> hook scripts to deal with something Subversion did to them is not a good
> answer.
>
Just to clarify: One only needs hook scripts if one wants to commit
to a 1.5 server and then repeat those commits (e.g., by using svnsync)
on a 1.6 server. In other cases --- 1.6-to-1.5 syncs, or upgraded
installations --- no hooks are needed.
Re conversion process: yes, will be useful (especially when versioned
props are involved). Once this (or another) thread reaches a conclusion
on the best strategy, we can document that somewhere.
> paul
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1456932
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1460148
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-28 22:24:48 CET