Brad Bonkoski wrote:
> Even if you all work from the trunk...
> Every user should have their own checked out version of the trunk, so
> if they decide to blow it away they would only affect their local
> copy, and not the repository (Or anyone else's checked out version of
> the trunk)....The beauty of source control.
His question was not about modifying a working copy. It was about making
changes in the repository view.
In repository view you are working directly against the repository and
not against your working copy.
>
> Of course you should consider the merge implications of having
> everyone work on the trunk, unless there are very clearly defined
> modules, even so it would probably be easier/safer for them each to
> work from their own branches, but that's just a side note....
>
> -B
>
>
> etornick wrote:
>
>> We are thinking about using subclipse for a large project. This
>> project will
>> have many developers, and some will be coming on board as newbies.
>> Additionally we are thinking of having a release manager be a
>> coordinator of
>> the creation of the branches and tags.
>>
>> For the most part, the developers will be working off the trunk until we
>> start gettting into more formal release procedures, then people might be
>> assigned to work on a branch for a specific maintenance release etc...
>>
>> What concerns me is that it seems incredibly easy to go into the
>> repository
>> view and select a folder (like the branches folder - (using the
>> suggested
>> subversion folder layouts of branches - tags - trunk....)) and right
>> click
>> and delete!!! You could blow away 50 branches this way!
>>
>> I experimented with this a bit and it really did the delete from the
>> "eclipse perspective". The project in another eclipse workspace
>> seemed to be
>> orphaned because when I tried a team->synchronize it said there was
>> nothing
>> to synchronize with.
>>
>> I figured there must be a way to control this so that certain people
>> could
>> be restricted to doing certain operations and it seems like the
>> "hooks" were
>> the only way.
>>
>>
>> Any ideas/thoughts on how to deal with this issue would be greatly
>> appreciated.
>>
>> Thanks,
>> Ed
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Feb 16 20:16:34 2006