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

RE: Re: svn:global-ignores

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Wed, 18 Sep 2013 15:51:23 +0000

> On 18 September 2013 14:36, Dan Lasley <dlasley_at_milleredge.com> wrote:
> > OK, let me try again.
> >
> > If I look at the TSVN properties in any folder in c:\projects\ it has svn:global-
> ignore set to ignore *.OBJ and *.LST.
> >
> > When I go to Import my project for the first time, uploading it to my web-host
> repository, the LST and OBJ files get uploaded and "versioned". This is not the
> desired result.
> >
> > What do I need to do to get these settings to apply?
> Any svn: property applies only to a versioned working copy. At the time when
> you do the import you have no working copy as you are creating a new project
> in the repository, so there is nowhere to hang these properties onto. The point
> of these properties is to allow you to ignore files within an already-versioned
> working copy structure.
> They do not and cannot work on import.
> By contrast the global ignores in TSVN's settings are always there and can be
> applied to imports.
> Subversion has no mechanism, when you import a new project into the
> repository, to tell you what files to ignore.

In 1.8.x that isn't correct. I just tested this.

I created a folder in my test repository named "root". I added the svn:global-ignores property to it with *.obj *.bu. (this could just as easily have been trunk)

I created a local folder rootbob and created 3 files in it, one with .txt, one with .obj, one with .bu extensions. I right clicked and chose import, put a path of ^/root/bob and clicked ok. As expected only the .txt file was added, the other two were properly ignored.

> You can set up a server-side pre-
> commit hook to reject commits which include such files, but it would be a
> sledgehammer solution and occasionally you may need to version a file which
> would normally be ignored.
> Personally I never use import at all. The manual describes a 2-stage import
> process whereby you first create an empty folder in your repository and
> checkout on top of your existing project folder. This makes the project folder,
> but not its content, versioned. You can then add svn:ignore properties, and also
> use the Add dialog to cherry pick which files you want to include.
> Simon

That said, I do agree that if you want to end up with a working directory import is two steps... It is better to create the folder in the repo browser, check it out to the folder you want to import using --force and then doing an add. This way you end up with a working copy.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-09-18 17:51:30 CEST

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

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