You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by kf...@collab.net on 2004/09/01 13:32:29 UTC
Re: [PATCH] FAQ suggestion - another minor proposal
Folker Schamel <sc...@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
> +
> +<pre>
> +svn update mydir/*
> +svn update mydir
> +</pre>
> +
> +This will fix all files in this directory at once.</p>
This advice might update other things underneath mydir/ as well. 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. 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 :-).
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] FAQ suggestion - another minor proposal
Posted by Folker Schamel <sc...@spinor.com>.
kfogel@collab.net wrote:
> Folker Schamel <sc...@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.
Take a look at the SECOND command:
Also the current FAQ suggests to use a "update" == "update ."
after the "update file.java", and therefore you anyway update everything.
And its hard to get rid of it, except you don't want to get the
correct versions of the problematic files, but then people
anyway wouldn't run into the "file is alreay existing" error,
and therefor don't have a problem to fix anyway,
and therefore won't do anything.
And as far as I know, "update -N" is problematic, right?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] FAQ suggestion - another minor proposal
Posted by kf...@collab.net.
Folker Schamel <sc...@spinor.com> writes:
> 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.
How did I not see that?
I'll fix.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] FAQ suggestion - another minor proposal
Posted by Folker Schamel <sc...@spinor.com>.
kfogel@collab.net wrote:
> Folker Schamel <sc...@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
Re: [PATCH] FAQ suggestion - another minor proposal
Posted by kf...@collab.net.
Folker Schamel <sc...@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
think.
-Karl
> 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
[PATCH] FAQ suggestion - another minor proposal
Posted by Folker Schamel <sc...@spinor.com>.
kfogel@collab.net wrote:
> Folker Schamel <sc...@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.
Cheers,
Folker
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
Re: [PATCH] FAQ suggestion - another minor proposal
Posted by kf...@collab.net.
Folker Schamel <sc...@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.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] FAQ suggestion - another minor proposal
Posted by Folker Schamel <sc...@spinor.com>.
kfogel@collab.net wrote:
> Folker Schamel <sc...@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
>>+
>>+<pre>
>>+svn update mydir/*
>>+svn update mydir
>>+</pre>
>>+
>>+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 :-).
Right.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org