create different ssh key according the article Mac Set-Up Git
$ ssh-keygen -t rsa -C "your_email@youremail.com"
create different ssh key according the article Mac Set-Up Git
$ ssh-keygen -t rsa -C "your_email@youremail.com"
| #!/bin/bash | |
| # Sometimes you need to move your existing git repository | |
| # to a new remote repository (/new remote origin). | |
| # Here are a simple and quick steps that does exactly this. | |
| # | |
| # Let's assume we call "old repo" the repository you wish | |
| # to move, and "new repo" the one you wish to move to. | |
| # | |
| ### Step 1. Make sure you have a local copy of all "old repo" | |
| ### branches and tags. |
| #!/usr/bin/env python | |
| import os | |
| import urllib2 | |
| import json | |
| import subprocess | |
| user=None | |
| repo=None |
Long ago, the first time I read "The Pragmatic Programmer", I read some advice that really stuck with me.
"Don't Use Manual Procedures".
This in the chapter on Ubiquitous Automation. To summarize, they want you to automate all the things.
The trouble was that I hadn't much of an idea how to actually go
| # Wrappers for pyvenv | |
| # | |
| # Source in .bashrc via 'source pyvenv-wrapper.sh' | |
| PYVENV_DIR=$HOME/.pyvenv | |
| PYVENV_BIN=pyvenv-3.4 | |
| function py-create-venv { | |
| mkdir -p $PYVENV_DIR | |
| $PYVENV_BIN $PYVENV_DIR/$1 |
| apply plugin: 'com.android.application' | |
| android { | |
| compileSdkVersion 21 // verify current sdk | |
| buildToolsVersion '20.0.0' // verify tools version | |
| defaultConfig { | |
| applicationId 'your complete package - equal manifest' | |
| minSdkVersion 11 | |
| targetSdkVersion 21 |