[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] FAQ suggestion - another minor proposal

From: Folker Schamel <schamel23_at_spinor.com>
Date: 2004-09-17 18:27:22 CEST

kfogel@collab.net wrote:
> Folker Schamel <schamel23@spinor.com> writes:
>
>>>>The "*" variant doesn't do anything else; it does it only in a simpler way.
>>>
>>>Not quite. "*" includes files whose case is fine, but which may
>>>receive updates from the server simply because they're out of date.
>>>The same thing could happen to the case-problematic files, of course,
>>>but at least it will be limited to them.
>>
>>Not correct -> don't forget the SECOND "svn update" command.
>>
>>Since this upper/lower-case issue is a quite common problem
>>for windows users, I suggest to at least add the simpler solution
>>to the FAQ, for example by using the patch below.
>
>
> This just has the same properties I described (of including more files
> than just the case-problematic ones), except to an even greater
> degree, since it does "update *" and then "update" on the entire dir.

no no no no no ;-)

Both

     svn update file.java
     svn update

and

     svn update *
     svn update

BOTH update the entire dir.
You cannot avoid this, because you need the second "svn update"
to fetch the missing files having the correct case.

> I don't object to putting the recipe in the FAQ, but it needs an
> explanation of why it works and what other effects it might have, I
> think.

Better explanation is always good;
but it is exactly the same for both variants.
Except that you might want to explain what the meaning of "*" is.

Really:
The "*" has no disadvantages, only advantages.
Take a closer look at it! ;-)

Cheers,
Folker

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 17 18:27:30 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.