A good commit message looks like this:
Header line: explaining the commit in one line
Body of commit message is a few lines of text, explaining things
in more detail, possibly giving some background about the issue
being fixed, etc etc.
The body of the commit message can be several paragraphs, and
please do proper word-wrap and keep columns shorter than about
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset=utf-8 /> | |
| <title>A Graph</title> | |
| <!--[if IE]> | |
| <script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script> | |
| <![endif]--> | |
| <style> | |
| article, aside, figure, footer, header, hgroup, |
| * { | |
| /* makes border and padding grow inward from width & height | |
| - mix-and-match units for various box model properties | |
| - ex. width: 25%; padding: 15px; | |
| - no workie in IE7 | |
| */ | |
| -moz-box-sizing: border-box; | |
| box-sizing: border-box; | |
| /* hiding overflow creates a block formatting context |
This document lays out some baseline expectations between conference speakers and conference presenters. The general goal is to maximize the value the conference provides to its attendees and community and to let speakers know what they might reasonably expect from a conference.
We believe that all speakers should reasonably expect these things, not just speakers who are known to draw large crowds, because no one is a rockstar but more people should have the chance to be one. We believe that conferences are better -- and, dare we say, more diverse -- when the people speaking are not just the people who can afford to get themselves there, either because their company paid or they foot the bill themselves. Basically, this isn't a rock show rider, it's some ideas that should help get the voices of lesser known folks heard.
These expectations should serve as a starting point for discussion between speaker and organizer. They are not a list of demands; they are a list of rea
| curl -s https://api.github.com/orgs/twitter/repos?per_page=200 | ruby -rubygems -e 'require "json"; JSON.load(STDIN.read).each { |repo| %x[git clone #{repo["ssh_url"]} ]}' |
#Node - File Paths
##File Paths Node has a path module which can be used to manipulate paths.
###Normalizing Paths Paths can be stored in different ways and it is neccessary to ensure that the path is standardized.
var path = require('path');
path.normalize('/foo/bar//baz/asdf/quux/..');
| // | |
| // returns a list of all elements under the cursor | |
| // | |
| function elementsFromPoint(x,y) { | |
| var elements = [], previousPointerEvents = [], current, i, d; | |
| // get all elements via elementFromPoint, and remove them from hit-testing in order | |
| while ((current = document.elementFromPoint(x,y)) && elements.indexOf(current)===-1 && current != null) { | |
| // push the element and its current style |
| # Run this one-liner from the Sublime Text console if you need to revert all open documents | |
| [ view.run_command('revert') for view in sublime.Window.views(sublime.active_window()) ] |
| #!/usr/bin/python | |
| ''' | |
| Python implementation of passcode hashing algorithm used on the Samsung Galaxy S4 GT-I9505 4.2.2 | |
| Correct PIN for hash and salt below is 1234. | |
| Get 40-character hash value in ascii hex format from file /data/system/password.key on the phone | |
| Get salt in signed numeric format by doing sqlite3 query SELECT value FROM locksettings WHERE name = 'lockscreen.password_salt' on /data/system/locksettings.db |
| 'getOwnPropertyDescriptors' in Object || ( | |
| Object.getOwnPropertyDescriptors = function (Object) { | |
| var | |
| gOPD = Object.getOwnPropertyDescriptor, | |
| gOPN = Object.getOwnPropertyNames, | |
| gOPS = Object.getOwnPropertySymbols, | |
| gNS = gOPS ? function (object) { | |
| return gOPN(object).concat(gOPS(object)); | |
| } : | |
| gOPN, |