From the command line: git checkout is probably what you want. The documentation shows an example of: $ git checkout master~2 Makefile to revert Makefile to two revisions back in the master branch From within TortoiseGit (via Windows Explorer) it looks like you can do this with the following steps: Navigate in Explorer to the … Read more
Two ways: Embed $Id$ or $Revision$ within the code. Then set svn:keywords=”Id Revision” property on the file. This will give you the last modified revision of that source file. Good for smaller projects and scripts. Alternatively, use a Makefile driven process and the command line tool svnversion. (Language specific – this should work for C/C++) … Read more
Try svn diff -r 5000:6001 instead. To understand this, consider the following: what would the output of svn diff -r 100:100 look like? It would show no changes, because the revisions are the same. To see the changes for revision 100, we must use -r 99:100.
You could use svn log, with a reverse revision range: svn log -r 1:HEAD –limit 1 <REPO_URL>
Github has a help page about removing sensitive data: http://help.github.com/removing-sensitive-data/ As gists are just git repositories, you should be able to locally clone your gist, do the clean-up there and do a forced push to overwrite the github version with the cleaned repo. Yes, after thinking about it: If <commit> is the commit you want … Read more
What worked for me was: android list sdk -a Which showed me the following list: 1- Android SDK Tools, revision 24.0.2 2- Android SDK Platform-tools, revision 21 3- Android SDK Build-tools, revision 21.1.2 4- Android SDK Build-tools, revision 21.1.1 5- Android SDK Build-tools, revision 21.1 6- Android SDK Build-tools, revision 21.0.2 7- Android SDK Build-tools, … Read more
There are several ways to do that. But do not just update to the earlier revision as suggested here. The easiest way to revert the changes from a single revision, or from a range of revisions, is to use the revision log dialog. This is also the method to use of you want to discard … Read more
From the command line, the –stop-on-copy flag can be used to help show you where you copied a branch from: svn log –stop-on-copy –verbose –limit 1 -r0:HEAD ^/branches/feature (where feature is the name of your branch) The last line of will say something like this: Changed paths: A /branches/feature (from /trunk:1234)
hg log file hg diff -r 10 -r 20 file
Try: hg id -i Example: $ hg id -i adc56745e928