Explore >> Select a destination
|
You are here 
|
blog.waleedkhan.name | ||
| | | | |
qsantos.fr
|
|
| | | | | ||
| | | | |
wpsoftware.net
|
|
| | | | | ||
| | | | |
www.jeremykun.com
|
|
| | | | | Recently my employer (Google) forced me to switch to Mercurial instead of my usual version control system, git. The process of switching sparked a few discussions between me and my colleagues about the value of various version control systems. A question like "what benefit does git provide over Mercurial" yielded no clear answers, suggesting many developers don't know. An informal Twitter survey didn't refute this claim. A distinguished value git provides me is the ability to sculpt code changes into stories. | |
| | | | |
citizen428.net
|
|
| | | I originally wrote this article for Codementor in October 2014. It should have something for everyone, from fairly new git users to experienced developers. 1. Discard local file modifications Sometimes the best way to get a feel for a problem is diving in and playing around with the code. Unfortunately, the changes made in the process sometimes turn out to be less than optimal, in which case reverting the file to its original state can be the fastest and easiest solution: | ||
