Thanks!

To git@git.d2evs.net:~ecs/tm
   e7732d3..ff0b73c  master -> master

Pushed with some minor fixups, you'll want to
`git config --global pull.rebase true` and
`git reset --hard origin/master` after pulling.

You still haven't squashed your commits.

Squash this with the previous commit - you can use `git rebase -i` and
replace the 'pick' on all but the last commit with 'fixup', then use
`git commit --amend --reset-author` (--reset-author because the
authorship of the previous patch was wrong) to fix the subject.

On Sat Nov 7, 2020 at 1:27 AM EDT, evantj wrote:
> ---
> lib.sh | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/lib.sh b/lib.sh
> index 3c48210..07d0e4e 100644
> --- a/lib.sh
> +++ b/lib.sh

s/mktmp/mktemp in patch name and use the imperative case.

On Sat Nov 7, 2020 at 12:58 AM EDT, evantj wrote:
> ---
> lib.sh | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/lib.sh b/lib.sh
> index c92e5ae..3c48210 100644
> --- a/lib.sh
> +++ b/lib.sh
> @@ -65,7 +65,12 @@ export TM_WS="${TM_WS:-$TM_DIR/..}"
> export TM_IGNORE="${TM_IGNORE:-$TM_WS/.tmignore}"
>  

On Tue Nov 3, 2020 at 8:43 PM EDT, Evan Johnston wrote:
> no, I can't

It worked \o\ /o/ \o\ /o/

Hello, world!

To make sure I haven't fucked up my mail server

Please rebase this off of master, there's no IDFK_WHERE_TO_PUT_THIS_EYAL
anymore.