[source]
This manual page is for Mac OS X version 10.9
If you are running a different version of Mac OS X, view the documentation locally:
In Terminal, using the man(1) command
Reading manual pages
# My pretty prompt: | |
# - Truncates the first few dirs in long paths | |
# - red/green prompt based on return value of previous command | |
# - inserts git branch name if in a repo | |
# Developed primarily for debian/ubunu systems | |
# First, some stuff from the Ubunutu .bashrc | |
# set variable identifying the chroot you work in (used in the prompt below) | |
if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then |
[source]
This manual page is for Mac OS X version 10.9
If you are running a different version of Mac OS X, view the documentation locally:
In Terminal, using the man(1) command
Reading manual pages
// install entware | |
installentware // for coreelec | |
wget -O - http://bin.entware.net/armv7sf-k3.2/installer/generic.sh | sh // for libreelec rasbperry 3 | |
// update && install zerotier | |
opkg update | |
opkg install zerotier | |
// start the daemon |
# this located in /storage/.config/autostart.sh on a CoreELEC box, run chmod +x to make it executable | |
# use nohup to run the script in the backgroud | |
# nohup /storage/freemyip/updateDynDNS.sh & | |
# use this to run once off tasks | |
( | |
# pause few seconds to wait for network & time services to start | |
sleep 5 | |
DT=$(date +"%m-%d-%Y, %r") | |
echo "Box rebooted on $DT, running tasks in autostart.sh" >> /storage/freemyip/DynDNSUpdate.log |
// List all remotely tracked branches that do not exist in the remote repo | |
git remote prune origin --dry-run | |
// Prune all remotely tracked branches that do not exist in the remote repo | |
git remote prune origin | |
// List all local branches that were merged into master, explicitly exclude master from that list | |
git branch --merged master | grep -v 'master' | |
/* |
Route all traffic with a raspberry pi like a VPN.
de | |
a | |
o | |
que | |
e | |
do | |
da | |
em | |
um | |
para |
This is way more complicated than it should be. The following conditions need to be met :
In this particular case, I'm interested in bringing in the 'default' template of jsdoc as a sub-directory in my project so I could potentially make changes to the markup it genereates while also being able to update from upstream if there are changes. Ideally their template should be a separate repo added to jsdoc via a submodule -- this way I could fork it and things would be much easier.... but, it is what it is.
After much struggling with git, subtree and git-subtree, I ended up finding this http://archive.h2ik.co/2011/03/having-fun-with-git-subtree/ -- it basically sets up separate branches from tracking remote, the particular sub-directory, and uses git subtree contrib module to pull it all togther. Following are