hg status –rev x:y where x and y are desired revision numbers (or tag or branch names). If you are using the terminal in windows add hg status –rev x:y> your-file.txt to save the list to a file.
Saving it in source control is more trouble than it’s worth. You have to do a commit every time you do a build for it to be any value. Generally we leave generated code( idl, jaxb stuff, etc) outside source control where I work and it’s never been a problem
The usual method I have seen is X.Y.Z, which generally corresponds to major.minor.patch: Major version numbers change whenever there is some significant change being introduced. For example, a large or potentially backward-incompatible change to a software package. Minor version numbers change when a new, minor feature is introduced or when a set of smaller features … Read more
The biggest difference is how the branch names are recorded in the history. With named branches the branch name is embedded in each changeset and will thus become an immutable part of the history. With clones there will be no permanent record of where a particular changeset came from. This means that clones are great … Read more
You can specify the files on the command line, as tonfa writes: $ hg commit foo.c foo.h dir/ That just works and that’s what I do all the time. You can also use the –include flag that you’ve found, and you can use it several times like this: $ hg commit -I foo.c -I “**/*.h” … Read more
We have a FAQ article covering this question. [The .idea] format is used by all the recent IDE versions by default. Here is what you need to share: All the files under .idea directory in the project root except the workspace.xml and tasks.xml files which store user specific settings All the .iml module files that … Read more
Most helpful Answer There is a plugin called SCM Sync configuration plugin. Original Answer Have a look at my answer to a similar question. The basic idea is to use the filesystem-scm-plugin to detect changes to the xml-files. Your second part would be committing the changes to SVN. EDIT: If you find a way to … Read more
Alternately: syntax: glob bin/**
I have tried both methods with a large commercial application. The answer to which method is better is highly dependent on your exact situation, but I will write what my overall experience has shown so far. The better method overall (in my experience): The trunk should be always stable. Here are some guidelines and benefits … Read more
Use the tf.exe tool from the Visual studio commandline – it can handle wildcards: tf.exe move <olditem> <newitem> Example: tf.exe move “$/My Project/V*” “$/My Project/Archive” [EDIT] As noted in the comments: move is an alias for rename. Both commands move history.