Re: [Scribia-dev] Re: CL: Scribus

[Charles L. <da...@sy...>]

>> i just tried to commit something but i don't have write access.
>
>You need to open a customer support item with SF (see recent email messags
>by Geotzou). Be warned that their support staff is sometimes less capable
>than your average drive-thru clerk.

i did, but it didn't seem to do any good. how can i find my old support
item? i'd like to see what the guy said. (as if it'll help.)

i'll try to open another support item. maybe they'll get tired of us and
finally give us pserver access. :)

>> also, i'd like some more information on CVS itself. i'm not sure i fully
>> understand how i am supposed to use this as a version control tool. for
>> example, when you want to work on a file, aren't you supposed to lock it so
>> that others do not change it at the same time? if so, i don't see any lock
>> option in MacCVS Pro.
>
>CVS is optimistic in the sense that it allows multiple people to
>concurrently (the C in CVS) edit the same files. It will guarantee
>consistency by automatically merging changes upon committing, unless the
>same line(s) have been edited by multiple parties. (In that case, you'll
>need to do manual conflict resolution, i.e. merge the changes by hand - but
>it doesn't happen often normally.) Locks are only used in the brief periods
>when someone is updating from or committing to the central repository.

ok. i am more used to VCS tools that allow exclusive locks to take place to
ensure that no one is fiddling with your source (SourceSafe, StarTeam). i
guess it's just another way of doing it.

>If you know Unix, CVS started as a bunch of shell scripts integrating RCS
>with diff/patch and related tools. If that means anything to you, you'll
>have some idea of how CVS works.

yeah, i get the idea.


--

charles lechasseur - da...@sy...
http://www3.sympatico.ca/danov/marathon/

  "The butts of evil are awaiting my bootprints!"
     - Minsc