Guten Tag C M,
am Freitag, 15. Februar 2013 um 17:38 schrieben Sie:
> Am I missing something here?
Maybe svn help import.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon.
On Fri, Feb 15, 2013 at 10:38 AM, C M wrote:
>
> I need to add new files to my project. Is there a way to create an empty
> working copy where I just copy the new files into it and then commit them?
>
> It seems unnecessary to have to checkout the whole project (or parts of it)
> to the working co
Dear All,
I need to add new files to my project. Is there a way to create an empty
working copy where I just copy the new files into it and then commit them?
It seems unnecessary to have to checkout the whole project (or parts of it)
to the working copy when I don't need to update anything existi
On Fri, Feb 15, 2013 at 12:21:16PM +0100, Diggory Hardy wrote:
> Dear list,
>
> I have an old checkout of an svn repo. This results in:
>
> L10036 mmBackend$ svn info
> svn: E155036: Please see the 'svn upgrade' command
> svn: E155036: Working copy '/home/dhardy/code/all/mmBackend' is too old
>
Diggory Hardy wrote on Fri, Feb 15, 2013 at 12:21:16 +0100:
> Ideally 'svn info' and 'svn st' should work on old checkouts without
> requiring
> any changes (upgrades or other) to them.
Yes we know, and we would have liked that too. It just wasn't possible
to implement in a timely or maintainab
Dear list,
I have an old checkout of an svn repo. This results in:
L10036 mmBackend$ svn info
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: Working copy '/home/dhardy/code/all/mmBackend' is too old
(format 10, created by Subversion 1.6)
L10036 mmBackend$ svn st
svn: E155036: P