2011/2/16 Thorsten Schöning <tschoening_at_am-soft.de>:
> Guten Tag Greg Long,
> am Mittwoch, 16. Februar 2011 um 13:15 schrieben Sie:
>
>> I think you misunderstand. It is OK for all authorized users to commit
>> releases. What I am trying to accomplish is to make all files in a
>> working copy of a release branch read-only.
>
> Just for my interest, but what is the use case you're trying to
> accomplish? In the end every developer can clear read only attributes
> in his working copy as will. Is the benefit that Windows Explorer, an
> editor etc. shows error message whenever one tries to edit the files?
> Is it for some kind of build process?
The files are basically csv files. The software that is used to open
them will make random (and innocuous) changes to one of its internal
columns.
So every time the software is run, the files are marked as changed
when nothing has really changed. If the files are marked read-only,
the software respects that and functions just fine.
This is something that we have to deal with in the development copies,
but would like to insulate the users from this annoyance.
We make extensive use of svn:externals where most of the externals are
released copies. When the user commits their local changes, the
changed external releases will cause the commit to fail.
Greg
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning
> AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig
>
> Telefon: Potsdam: 0331-743881-0
> E-Mail: tschoening_at_am-soft.de
> Web: http://www.am-soft.de
>
> AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam
> Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow
>
>
Received on 2011-02-16 20:10:40 CET