The simple answer is that you svn export the file instead of checking it out. But that might not be what you want. You might want to work on the file and check it back in, without having to download GB of junk you don’t need. If you have Subversion 1.5+, then do a sparse … Read more
Subversion does not have a built-in “do not commit”https://stackoverflow.com/”ignore on commit” feature, as of February 2016 / version 1.9. This answer is a non-ideal command-line workaround As the OP states, TortoiseSVN has a built in changelist, “ignore-on-commit”, which is automatically excluded from commits. The command-line client does not have this, so you need to use … Read more
The fundamental difference is the composition rule. In a true component-based approach, you define a configuration, that is: The list of labels (of SHA1 commits for Git) you need for your project to “work” (i.e. “develop”, “compile”, “deploy”, …). Each commit referenced in a configuration helps you to get the exact versions of all trees. … Read more
I needed this as well, and with the help of Bombe’s answer + some fiddling around, I got it working. Here’s the recipe: Import Git -> Subversion 1. cd /path/to/git/localrepo 2. svn mkdir –parents protocol:///path/to/repo/PROJECT/trunk -m “Importing git repo” 3. git svn init protocol:///path/to/repo/PROJECT -s 4. git svn fetch 5. git rebase origin/trunk 5.1. git … Read more
I have been where you are now, sceptical of the uses of distributed version control. I had read all the articles and knew the theoretical arguments, but I was not convinced. Until, one day, I typed git init and suddenly found myself inside a git repository. I suggest you do the same — simply try … Read more
Git is not better than Subversion. But is also not worse. It’s different. The key difference is that it is decentralized. Imagine you are a developer on the road, you develop on your laptop and you want to have source control so that you can go back 3 hours. With Subversion, you have a Problem: … Read more
Lee B was right. The answer, provided by doener in #git, is to upgrade Git to 1.6.x (I had been using 1.5.x). 1.6.x offers deep cloning so that multiple wildcards can be used with the –branches option: $ git svn clone https://svn.myrepos.com/myproject web-self-serve \ –trunk=trunk –branches=branches/*/* –prefix=svn/ $ git branch -r svn/development/sandbox1 svn/development/feature1 svn/development/sandbox2 svn/development/sandbox3 … Read more
(This answer has been updated to match SVN 1.8 and 1.9’s behaviour) You have 2 questions: Marking files as ignored: By “ignored file” I mean the file won’t appear in lists even as “unversioned”: your SVN client will pretend the file doesn’t exist at all in the filesystem. Ignored files are specified by a “file … Read more
Set the svn:ignore property of the parent directory: svn propset svn:ignore dirname . If you have multiple things to ignore, separate by newlines in the property value. In that case it’s easier to edit the property value using an external editor: svn propedit svn:ignore .
Hmm, not sure I agree with Nick re tag being similar to a branch. A tag is just a marker Trunk would be the main body of development, originating from the start of the project until the present. Branch will be a copy of code derived from a certain point in the trunk that is … Read more