On Dec 21, 2004, at 6:30 AM, Erik Huelsmann wrote:
>>>> BTW, CodeWarrior (unfortunately) depends on the files being
>>>> in order to be considered unmodified. I heard somewhere that
>>>> Subversion 1.2 will support read-only checkouts. Is this true and
>>>> there a timeframe for 1.2?
>>> Subversion 1.2 will support locking. Currently development is still
>>> going on, but a preliminary estimate for 1.2 is given on the
>> He doesn't mean locking, he's looking for read-only checkouts
>> (files are
>> flagged read only by SVN when they are unchanged). This is a
>> feature which
>> would also require... will that be in 1.2?
> If you don't mean files needing locks and signalling that by setting
> read-only, then I guess it's currently not planned.
> But to say it won't be in 1.2, that depends on what exactly you expect
> Subversion, how easily that could be implemented and whether someone
> will be
> taking up that task before then.
> So, if you want something like this, could you define the expected
> and have a discussion about that on dev@? That's the way we work on
> I'm thinking about behaviours+reasons like:
> - In what respect does CodeWarrior (or your tool) treat read-only files
> differently than read-write files?
It won't let you edit them until you choose "edit" or "unlock".
> - When should files be set read-write, when read-only?
Only when the user/plugin says "edit" or "unlock".
> - When is it ok to overwrite a read-only file?
> - If a file is copied, does it retain it's attributes?
> - Does that include read-onlyness?
I would think.
> - How do directories fall into this picture?
Directories are candidates for locking, AFAICT.
Let me read through the current locking documents and then post a real
analysis to dev. As Ben suggested, it may do everything I want but it
also looks significantly more complex than what I am looking for.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Dec 21 19:30:45 2004