Installation:
Home brew packages:
$ brew install \
coreutils \
Installation:
Home brew packages:
$ brew install \
coreutils \
Merge project/repos-b
in project/repos-a
in repos-b
subdirectory:
$ git clone [email protected]:project/repos-a.git
$ cd repos-a
$ git remote add -f repos-a [email protected]:project/repos-b.git
$ git merge -s ours --allow-unrelated-histories --no-commit repos-b/master
$ git read-tree --prefix=repos-b/ -u repos-b/master
$ git commit -m "Merge repos-b as our subdirectory"
$ git pull --allow-unrelated-histories -s subtree repos-b master
#!/bin/bash | |
set -T | |
trap 'echo "> $BASH_COMMAND"' DEBUG | |
i=1234 | |
echo "$i" | |
(echo $i) |
From time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that's bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck:
There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don't want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees.
That needs to stop immediately or I will take drastic action - I have given enough warning over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary.
#!/usr/bin/env bash | |
# curl ... | bash | |
set -e | |
# make in case they aren't already there | |
mkdir -p "/usr/local/lib" | |
mkdir -p "/usr/local/bin" | |
# Check for Homebrew, |