Some subversion repositories will group logically unrelated things (i.e. projects with different version numbers and release cycles) under one trunk: . |– branches | |– project-a-1.x | `– project-a-feature-1 |– tags | |– project-a-1.0 | |– project-b-1.0 | `– project-b-1.1 `– trunk |– project-a `– project-b This kind of layout has no direct analog in … Read more
One argument for using –no-metadata is that it doesn’t change your commit messages. So even if you fetch from different locations, the commit messages will be the same and thus the commit hashes will be the same. As an example, if I git svn init a repo from a local file: URL and later pull … Read more
I experienced something similar recently but excluding and then re-including the missing files didn’t work for me. In VS2013 Premium, I noticed there’s a “Untracked Files” section at the bottom of the Changes window. It was simply a matter of right-clicking the files I wanted to include and adding them. Not ideal, indeed, but another … Read more
I just launched a fossil hosting solution over at http://chiselapp.com It’s still in alpha but supports a number of things already. Feel free to let me know what you think.
On the top of my head: its distributed aspect (each developer has a copy of the repository) The ability to handle complex merges very quickly the possibility to switch from task to task, shelve his work, go back to it… cheap branching (instant switch: it just writes a few bits in a file! And it … Read more
The main pain point is in the “Distributed” aspect of any DVCS: you are cloning everything (the all history of all files) Since binaries aren’t stored in delta for most of them, and aren’t compressed as well as text file, if you are storing rapidly evolving binaries, you end up quickly with a large repository … Read more
To revert the working tree back to a specific revision N: bzr revert -rN To revert the working tree to the latest revision in the branch: bzr revert
Git makes it hard to lose work. Run: git reflog Than look for the commit that was just before the rebase Then check it out git checkout <sha> Look around, is it the version you wanted to recover? If so, create a branch here git checkout -b mybranch
It doesn’t track them. That’s the beauty of it. Git only records snapshots of the entire project tree: here’s what all files looked like before the commit and here’s how they look like after. How we got from here to there, Git doesn’t care. This allows intelligent tools to be written after a commit has … Read more