Nathan Hartman to Anton Shepelev:
> > That was my initial suggestion, too, but when I tried `svn up'
> > at a random location that was not an SVN working directory it
> > printed:
> >
> > Skipped '.'
> > Summary of conflicts:
> > Skipped paths: 1
> >
> > which is not very polite. I expecte
On Wed, Apr 29, 2020 at 6:42 PM Anton Shepelev wrote:
>
> Nathan Hartman:
>
> > If the command line client, are you in a working copy directory
> > when you run the "svn update" command?
>
> That was my initial suggestion, too, but when I tried `svn up' at a
> random location that was not an SVN w
Nathan Hartman:
> If the command line client, are you in a working copy directory
> when you run the "svn update" command?
That was my initial suggestion, too, but when I tried `svn up' at a
random location that was not an SVN working directory it printed:
Skipped '.'
Summary of conflicts:
On Wed, Apr 29, 2020 at 1:10 PM Brandon Helsley
wrote:
> How do I update source if when I use Svn update it responds with svn:
> e155007 none of the targets are working copies.
>
Are you using the svn command line client or a GUI?
If the command line client, are you in a working copy directory w
How do I update source if when I use Svn update it responds with svn: e155007
none of the targets are working copies.
