On 7/20/06 at 11:39 AM, offby1@blarg.net (Eric Hanchrow) wrote:
> >>>>> "Andrew" == Andrew Brosnan <andrew@broscom.com> writes:
>
> Andrew> Hello, I'm setting up a project that will have some fairly
> Andrew> non-technical folks accessing some files under version
> Andrew> control. (For example designers and HTML files.) Changes
> Andrew> will be made on one working copy only
>
> > I would gently urge you to reconsider that -- that scheme loses many
> > of the benefits of version control.
I miss-spoke. The designer will make changes to one working copy only.
Those familiar with version control may use their own wc.
>
> Andrew> and I plan to automate/script commits and updates for
> Andrew> them. However, I wonder about the best way to handle adds
> Andrew> and deletes. I've considered parsing the output of status
> Andrew> and then issuing any needed commands. However I assume
> Andrew> there is a better way. Any suggestions?
>
> http://subversion.tigris.org/faq.html#working copy-change-detection
I see. The problem would be that copied files would loose their history,
correct? Still it might be reasonable to have the designer just modify,
add or delete files, (which is the bulk of what they do). Moves would
have to be done by someone in the know. Not ideal, but I guess there are
trade-offs when shooting for transparency. Sounds like autoversioning
with WebDAV is not yet without it's quirks either.
Thanks,
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 20 23:27:00 2006