On 4/27/07, Ingo Schmidt <firstname.lastname@example.org> wrote:
> Hi Andrew!
> > i saw the option for a global-ignores property in the config and
> > populated that with *.bak *.scc
> If you explicitly add a file that would match an ignored pattern,
> it will still get added.
> However, if such a file is in a folder and you "svn add" this folder,
> then it will be ignored.
> In your working copy you create a folder called "testfolder". In it a file
> called "test.bak". Now do "svn add testfolder". You will notice that
> test.bak is indeed ignored as expected.
> Now change into your testfolder and do "svn add test.bak" and you will
> see, that this time your file gets added.
> So someone must have explicitly added these files for you, or your
> config file is not yet correct. Which client did you use? Command
> line? TSVN?
> > but i'm thinking that since we're going to have to straddle two
> > source repositories for a couple months
> You are going to have both, VSS and SVN side by side? Is there maybe a
> way of making a cut one day and switch?
> I did just that the other day in my company and it worked like a
> charm. I did write a script, that automatically converts a VSS
> database to svn with the help of the vss2svn script.
> I did make a lot of "dry runs" to fine tune my script for our needs to
> make sure my script works perfectly on the day of the cut. It did and
> we switched from VSS to SVN over night and so far had no problems at
> all. :-)
> Maybe this is not an option in your case, but it could be worth
> considering this :-)
thanks so much for the reply. i am using Tortoise as the client so i
do have to specify the files even if i select a directory. i'll start
using the cl for the adds though, thanks for the tip. ;)
unfortunately we have to straddle the two repos because we have
several development teams/projects working on very unorganized code.
the project i'm working on is using our own codebase so we're
migrating to SVN. once our project goes live we'll be cutting
everyone else over to SVN (hopefully). so the only ppl that have to
deal with the straddle will be the devs on my team. but we're excited
about making it work so it shouldn't cause us too much pain.
i agree that it would be much easier to bring everyone on board at the
same time, especially since we'll be merging the other teams code into
ours along the way.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Apr 27 17:44:48 2007