On Aug 27, 2007, at 22:06, Matt Sickler wrote:
> On 8/27/07, CARASSO Felipe wrote:
>>> Well, at the least, you've introduced a new error state to deal
>>> In the current model the content folder must exist if the
>>> administration area exists (one is a file-system descendant
>>> of the other). In the proposed approach this is not the case
>>> so you have to either treat a missing content folder as
>>> missing content to be recreated during an update, evidence of
>>> a remove, or a working copy error.
>> Since the premisse is that only the versioned data was copied, and
>> not the control data (note that this is the goal of my proposal),
>> the assumption would be that when control is there and data isn't,
>> it means that a "delete" needs to be commited.
>> Note also that with the current model you copy versioned data
>> *and* control data, ending up with control data that has nothing
>> to do
>> with what's in the server. This is the motivation of my proposal.
> I think the error lies with the users, not the tool. Perhaps you can
> better educate those users who are having problems in the proper use
> of svn.
> I am curious though, how they copy and paste stuff, and not get the
> .svn folders. Are they doing the equivalent of moving / coping things
> around without telling svn (ie, using cp and mv instead of svn cp and
> svn mv) ??
> If that is the case, it would be much more efficient to tell the users
> the correct way to do it.
> If they are using tools like TortoiseSVN, its already built in to the
> right-click menu.
Exactly, Matt. The only reason I can think of why one would care
where Subversion stores its admin directories is that one is copying
and moving files using native OS commands instead of using svn cp and
svn mv. And that would be a user error. One must use svn cp and svn
mv. The book goes into it in some detail and there's also a relevant
Subversion is not a toaster. It's a complicated piece of machinery,
and only proper education of the users will result in its being used
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Aug 28 09:18:01 2007