Explore >> Select a destination


You are here

www.petecorey.com
| | www.paritybit.ca
1.3 parsecs away

Travel
| | I've recently overhauled a lot of the software I use which means I have a whole new set of configuration files for most of that software. I figured it would be a good time to change the way I manage these configuration files too.
| | shibumi.dev
2.2 parsecs away

Travel
| | How to handle your Linux/Mac dotfiles with git
| | hamatti.org
3.6 parsecs away

Travel
| | I love dotfiles and I love sharing. But I have this weird feeling that sharing my dotfiles is too intimate and personal.
| | citizen428.net
18.5 parsecs away

Travel
| 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: