TASIOMIND.DEV — OPERATIONAL▸▸▸FULL STACK DEVELOPER @ GWQ SERVICEPLUS AG▸▸▸FOUNDER — K8SGPT.AI▸▸▸OPEN SOURCE: ACTIVE▸▸▸DISTRIBUTED SYSTEMS / KUBERNETES / AI▸▸▸RUST + GO + PYTHON▸▸▸FIELD TESTED / STATUS — NOMINAL▸▸▸LOCATION: EUROPE/BERLIN▸▸▸TASIOMIND.DEV — OPERATIONAL▸▸▸FULL STACK DEVELOPER @ GWQ SERVICEPLUS AG▸▸▸FOUNDER — K8SGPT.AI▸▸▸OPEN SOURCE: ACTIVE▸▸▸DISTRIBUTED SYSTEMS / KUBERNETES / AI▸▸▸RUST + GO + PYTHON▸▸▸FIELD TESTED / STATUS — NOMINAL▸▸▸LOCATION: EUROPE/BERLIN▸▸▸
← git-github

Size differences between git clone, git clone --mirror and git clone --depth 1

June 22, 2020

Kurzvergleich

  • git clone = working copy + full history
  • git clone --mirror = bare repo + alle refs (gleiche History Groesse)
  • git clone --depth 1 = shallow clone, weniger History

Beispiel

code
git clone REPO_URL
git clone --mirror REPO_URL
git clone --depth 1 --no-single-branch REPO_URL

Hinweis

--mirror spart keinen Platz, es kopiert die komplette History. Nur --depth reduziert Daten.