dvcs

We are migrating from Clearcase to another VCS (probably either SVN or Mercurial). For companies that have made this transition, what factors did they find important in selecting another VCS tool, and what practices did they find eased the transition? SVN and Mercurial are both good SCM. Many opensource projects use them. If your choice only narrowed down to these two then what you and your team must consider is: Workflow and workflow How do you want to do the commits and branching? Distributed or Purely centralized? This is related to the company policy too. Go with SVN if you want everything

In our project files, if there are binary files, such as .doc, .xls, .jpg, and we choose to not keep their past revisions (just keeping a latest version is ok), is there a way to tell SVN, Git, or Mercurial or some other tool to skip the revisions for these files or for a particular folder? Say, there is a 4MB .doc file that I need to check in hundred of times, but I don't really care so much about its past versions. So if the system keeps 100 revisions of it, that's already 400MB... checking in 300 times means 1.2GB for 1 file and that's not good. Only the latest version is good so that

I want to know if there's a way to turn off the default push, but keep the default pull when using Mercurial. I don't want to accidentally pollute the master repository by inadvertently pushing from an experimental repository. Your solution probably is the quickest and is certainly effective. If there's any official way it would be using a preoutgoing hook: [hooks] preoutgoing = bash -c 'read -p "Really push to $HG_URL? " -n 1 RESP ; [ "$RESP" == "y" ]' which will ask you if you want to push and provide the URL to which it would go as a reminder. moswald I was able to solve this by putting the

In my local git tree I pull commits from the "master" branch in the repository, but all development is done in a different branch, and pushed in a different branch too. I would like to avoid mistakes and prevent accidental commits in my local "master" branch, and allow only pull requests (then I'd rebase the developement branch to the updated master). Is this possible? How? brice You can use a pre-commit hook . For example, place the following script as .git/hooks/pre-commit : #!/bin/bash if test $(git rev-parse --abbrev-ref HEAD) = "master" ; then echo "Cannot commit on master" exit 1 fi And

Considering switching to Mercurial or Git? We are too. I'm currently studying the benefits of DVCS which turn out to be vast, lust and must. I would love to hear from the community typical usage patterns. Let's create a "Top N" productivity feature list for DVCS (based on Mercurial, Git or alike). Please describe work flows that prove to be productive for you / your team, procedures that DVCS helped you achieve/improve as well as blunt "good stuff" that DVCS gives you (don't assume stuff are clear to the novice user). I think that such a list could help folks approaching the team with a DVCS

We can see all the changesets and the files involved using hg outgoing -v but the filenames are all scattered in the list of changesets. Is there a way to just see a list of all the files that will go out if hg push is issued? First, create a file with this content: changeset = "{files}" file = "{file}\n" Let's say you call it out-style.txt and put it in your home directory. Then you can give this command: hg -q outgoing --style ~/out-style.txt | sort -u A somewhat under-appreciated feature: hg status can show information about changes in file status between arbitrary changesets. This can be