[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-01 17:24:40 CEST

kfogel@collab.net wrote:

> Folker Schamel <schamel23@spinor.com> writes:
>>To avoid that in case of having multiple such files
>>(I know what I'm talking about! ;-)
>>each repository user is sitting in front of his computer
>>and typing "update file.java" and "update" for each single file
>>- and curse at svn unnecessarily ;-) - what about the following:
>>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
>>+svn update mydir/*
>>+svn update mydir
>>+This will fix all files in this directory at once.</p>
> This advice might update other things underneath mydir/ as well.

That's the same as for the single-file fix.

> Most
> users would realize that -- though the ones who wouldn't are exactly
> the ones who would be unlikely to figure out the "update *" method on
> their own.
> Rather than complicate the explanation further, I think it's better to
> give a simple recipe that works every time, does exactly what's needed
> to fix the case problem, and doesn't do anything else.

The "*" variant doesn't do anything else; it does it only in a simpler way.

> It's okay if
> the recipe is cumbersome. After all, the last piece of advice we give
> is that people should try to avoid being in this situation in the
> first place :-).


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