Everyone has their own individual repository, and each updates their own repository by getting change-sets from others. In a nutshell, it's kinda like emailing your changes to your team mates. It took me some time to wrap my head around the idea of a distributed VCS too. This article might help clear it up: Distributed revision control. I might be wrong, but I hope this sounds reasonable. This is mostly my reasoning based off a little experience with both. A repository is then created inside the new folder. SVNRepository Right click on the newly created folder and select TortoiseSVN Create Repository here. #Tortoisehg create repository from existing folder windows#The best you can do is check for incoming change-sets and view your local repository (using windows explorer). The TortoiseSVN menu for unversioned folders Open the windows explorer Create a new folder and name it e.g. There are actually multiple different repositories for a project located in many places, instead of a single one, so there isn't really any meaning to "exploring the repository". When you commit, you commit to your local repository, then you can push changes to other people or locations (such as google code, or your team mates). You will create a new Mercurial repository, create a new Java project and commit the changes. Run: C: ew\cd TESTREPO C: ew\TESTREPO\del. Another popular distributed version control systems is Git. In our 'new' directory run the following: C: ew\mkdir TESTREPO C: ew\svnadmin create TESTREPO Now you will have a repo in the 'TESTREPO' directory. So, the actual repository is your "checked out" copy. For this example our existing repo is 'TESTREPO' Go to your command line. I might be wrong as I have little experience with Hg myself, but I believe the reason TortoiseHg doesn't have a repository like its SVN counterpart is because Hg is a distributed VCS instead of a centralized VCS like SVN.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |