Read the statement by Michael Teeuw here.
So I have a question about backup
-
@sdetweil Awesome. Thanks Sam. Always nice work from you.
-
@sdetweil When I ran the mm_backup.sh I saw this error but it created the output in the
MM_backup
folder as expected.usage: git init [-q | --quiet] [--bare] [--template=<template-directory>] [--shared[=<permissions>]] [<directory>] --template <template-directory> directory from which templates will be used --bare create a bare repository --shared[=<permissions>] specify that the git repository is to be shared amongst several users -q, --quiet be quiet --separate-git-dir <gitdir> separate git dir from working tree
Is this because of some options that I did not specify? After the output was created I just manually pushed to a private directory on git.
-
@mumblebaj probably git version before 2.28
the primary branch name option didn’t come in til 2.28. 0
i have
git --version git version 2.34.1
I will add a check…
to upgrade git (don’t do it for these scripts… I have fixed the script to not need this capability, just documenting how)
sudo add-apt-repository -y ppa:git-core/ppa sudo apt update sudo apt install git -y
-
@mumblebaj I pushed a change to set the primary branch name a different way…
give it a try
backup to some other folder (and then u can delete that folder)
./mm_backup.sh -b somefolder
just pushed a change to create the output folder if it doesn’t exist, instead of error…
-
@sdetweil Awesome. That was clean.
-
@sdetweil My git version is 2.20.1. Guess I need to update it.
-
@mumblebaj said in So I have a question about backup:
Guess I need to update it.
only if u need something
-
@sdetweil Right now, not. MM runs perfect as is. I’ll leave it for now. :beaming_face_with_smiling_eyes:
-
@mumblebaj i don’t want to force people to upgrade, thanks for the report and test results
-
@sdetweil No worries and a pleasure.