Explore >> Select a destination
|
You are here 
|
blog.waleedkhan.name | ||
| | | | |
blog.bloomca.me
|
|
| | | | | The blog of Seva Zaikov | |
| | | | |
blog.kulman.sk
|
|
| | | | | When working on iOS applications, I often find myself in situations where I need to develop a new feature while simultaneously fixing a bug. This can be challenging to manage, especially when the changes for the feature and the bug fix overlap. Developers have different approaches to handle this: Stashing changes Creating temporary commits Cloning the repository twice While these methods work, they are not ideal. Recently, I discovered a better solution. | |
| | | | |
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. | |
| | | | |
www.blopig.com
|
|
| | | |||
