Explore >> Select a destination
|
You are here 
|
www.howardism.org | ||
| | | | |
notes.neeasade.net
|
|
| | | | | ||
| | | | |
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: | |
| | | | |
www.mgasch.com
|
|
| | | | | Ever wanted to contribute to an open source project but quickly got overwhelmed with git terminology? I'm glad you asked... | |
| | | | |
labanskoller.se
|
|
| | | Inpired by Hackeriet's blog where Alexander Kjäll use to post CTF write-ups, I've decided to create a personal one for myself. Focus will be on IT security. Hackeriet's blog is powered by Jekyll which is a static site generator written in Ruby. See their post Creating a fast blog for how they set up their blog. I have decided to try another static site generator called Hugo, which is written in Go. | ||
