Description: Setup GitHub Pages "gh-pages" branch and "master" branch as subfolders of a parent project folder ("grandmaster").
Author: Chris Jacob @_chrisjacob
Tutorial (Gist): https://gist.github.com/833223
ּ_בּ | |
בּ_בּ | |
טּ_טּ | |
כּ‗כּ | |
לּ_לּ | |
מּ_מּ | |
סּ_סּ | |
תּ_תּ | |
٩(×̯×)۶ | |
٩(̾●̮̮̃̾•̃̾)۶ |
Description: Setup GitHub Pages "gh-pages" branch and "master" branch as subfolders of a parent project folder ("grandmaster").
Author: Chris Jacob @_chrisjacob
Tutorial (Gist): https://gist.github.com/833223
import sys | |
from cStringIO import StringIO | |
sys.path = [ | |
'/opt/pypy-sandbox', | |
'/opt/pypy-sandbox/lib_pypy', | |
'/opt/pypy-sandbox/lib-python/modified-2.5.2', | |
'/opt/pypy-sandbox/lib-python/2.5.2', | |
'/opt/pypy-sandbox/lib-python/2.5.2/plat-linux2' | |
] |
This guide assumes a fresh install of Mac OSX 10.6 Snow Leopard or 10.7 Lion.
Follow https://github.com/mxcl/homebrew/wiki/installation to get the basic setup up and running. (the default, not the alternate installs)
The web is full of benchmarks showing the supernatural speed of Git even with very big repositories, but unfortunately they use the wrong variable. Size is not important, but the number of files in the repository really is!
Why is that? Well, that's because Git works in a very different way compared to Synergy. You don't have to checkout a file in order to edit it; Git will do that for you automatically. But at what price?
The price is that for every Git operation that requires to know which files changed (git status, git commmit, etc etc) an lstat() call will be executed for every single file
Wow! So how does that perform on a fairly large repository? Let's find out! For this example I will use an example project, which has 19384 files in 1326 folders.
"use strict"; | |
let recorder=require("micropilot").Micropilot("addressbar").start(); | |
let possibles = [ | |
"where to do today?", | |
"search or enter an address", | |
"your wish is my command" | |
]; |
// Start `node d3-server.js` | |
// Then visit http://localhost:1337/ | |
// | |
var d3 = require('d3'), | |
http = require('http') | |
http.createServer(function (req, res) { | |
// Chrome automatically sends a requests for favicons | |
// Looks like https://code.google.com/p/chromium/issues/detail?id=39402 isn't | |
// fixed or this is a regression. |
let { events: windowEvents } = require('sdk/window/events'); | |
let { on } = require('sdk/event/core'); | |
let { filter } = require('sdk/event/utils'); | |
let ready = filter(windowEvents, ({type}) => type === 'DOMContentLoaded'); | |
let certificateWindows = filter(ready, ({target}) => | |
target.document.documentElement.mozMatchesSelector('dialog#certDetails')); | |
on(certificateWindows, 'data', ({target: window}) => { |