[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: <kfogel_at_collab.net>
Date: 2004-09-17 15:28:45 CEST

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.

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


> Index: www/project_faq.html
> ===================================================================
> --- www/project_faq.html (revision 10785)
> +++ www/project_faq.html (working copy)
> @@ -1158,6 +1158,16 @@
> copy, the second update will add <tt>File.java</tt>, leaving you with
> a correct working copy.</p>
> +<p>If you have many such problematic files in a directory <tt>mydir</tt>,
> +you can use
> +
> +<pre>
> +svn update mydir/*
> +svn update mydir
> +</pre>
> +
> +This will fix all files in this directory at once.</p>

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 17 17:12:04 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.