Abhishek L theanalyst

Manage your gmail account in emacs with mu4e

There're a lot of combinations to manage your email with emacs, but this works for me. I've a backup and I can manage my daily email.

The stack:

emacs
offlineimap
mu
mu4e

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = [email protected]:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

(This is the text of the keynote I gave at Startup Riot 2009. Will update when video becomes available.)

Hi everyone, I'm Chris Wanstrath, and I'm one of the co-founders of GitHub.

GitHub, if you haven't heard of it, has been described as "Facebook for developers." Which is great when talking about GitHub as a website, but not so great when describing GitHub as a business. In fact, I think we're the polar opposite of Facebook as a business: we're small, never took investment, and actually make money. Some have even called us successful.

Which I've always wondered about. Success is very vague, right? Probably even relative. How do you define it?

After thinking for a while I came up with two criteria. The first is profitability. We employ four people full time, one person part time, have thousands of paying customers, and are still growing. In fact, our rate of growth is increasing - which means January was our best month so far, and February is looking pretty damn good.

	#!/usr/bin/env python
	"""Split large file into multiple pieces for upload to S3.

	S3 only supports 5Gb files for uploading directly, so for larger CloudBioLinux
	box images we need to use boto's multipart file support.

	This parallelizes the task over available cores using multiprocessing.

	Usage:
	s3_multipart_upload.py <file_to_transfer> <bucket_name> [<s3_key_name>]

	!-------------------------------------------------------------------------------
	! Xft settings
	!-------------------------------------------------------------------------------

	Xft.dpi: 96
	Xft.antialias: false
	Xft.rgba: rgb
	Xft.hinting: true
	Xft.hintstyle: hintslight

	# "Understanding Python's closures".
	#
	# Tested in Python 3.1.2
	#
	# General points:
	#
	# 1. Closured lexical environments are stored
	# in the property __closure__ of a function
	#
	# 2. If a function does not use free variables

	*.csv
	.cache