[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: internal dirs showing up on update

From: <kmradke_at_rockwellcollins.com>
Date: Fri, 18 Feb 2011 12:40:46 -0600

Nuno Carapeto <carapeto_at_gmail.com> wrote on 02/18/2011 12:19:39 PM:
> On Thu, Feb 17, 2011 at 8:56 PM, Blair Zajac <blair_at_orcaware.com> wrote:
> On 2/17/11 12:50 PM, Bob Archer wrote:
> I have so SVN repos (subversion) and I use them with no proble. But
> when we do updates/commints on client (tortoise) we always get teh
> internal directories:
> conf
> dav
> db
> hooks
> locks
> format
> README.txt
> These es are internal and should not appear right? How do I remove
> this?
> I assume these folder are in your repository. Just go into the
> repository browser in TortoiseSVn and delete the folders.
> It sounds like somebody checked in a copy of a repo into the repo,
> in which case it's safe to delete.
> Blair
> Ok!
> Thank you all for the support.
> As suggested I just deleted it and committed them and its working
> Still I found it odd that some random user would put them there when
> they don't actually know what folders are in the server.
> Plus it happened in at least 2 repos. I suspect some random client bug

We have found a number of users do this with TortoiseSVN.
They appear to be doing a "Create repository here", followed by an
"Import..." to the URL they were given, then finally understand what
they really wanted to do was a "SVN Checkout..."

"Checkout" seems to be a foreign concept (and apparently scary one) to
some new non-technical users and they seem to struggle their way
through a number of other more "inviting" steps before they find the
right one.

I've contemplated suggesting to the TortoiseSVN developers that they
should add a warning if an user tries to do an "Import..." with
a directory that contains an fsfs repository structure.

Kevin R.
Received on 2011-02-18 19:41:30 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.