[cvsnt] Safe reserved edit sequence

[Gerhard Fiedler]

Hi all,

I have a script to edit a number of binary files. The sequence I'm using is
edic -c, update, edit (I use read-only checkouts).

This sequence seems to be necessary, because
1- the first edit -c reserves the files
2- the update then makes sure they are up to date (if I ran the update
before the edit -c there is a small window of opportunity for a commit by
someone else between the update and the then following edit -c)
3- the final edit makes sure no files are read-only.

Do I see this correctly, or am I missing something?

Specifically, Tortoise uses a simpler sequence (update, edit -c). Is this
sequence safe?

Thanks,
Gerhard