Update git-backup.rst (#734)

Bare does not mean empty. From
https://git-scm.com/book/en/v2/Git-on-the-Server-Getting-Git-on-a-Server
"a new bare repository — a repository that doesn’t contain a working
directory".

Additionally corrected a typo: should be send -> should be sent
This commit is contained in:
7heo 2025-05-26 19:58:18 +02:00 committed by GitHub
parent b9900ff4eb
commit f11aed3f5d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -61,8 +61,9 @@ button in the user interface) is responsible for initialising the empty local re
.. Note::
One can always change the upstream target, as long as the newly configured one is either "bare" (empty) or containing the
exact same content (/change history) as the one used on this firewall.
One can always change the upstream target, as long as the newly configured one is either empty (has absolutely no history
- otherwise said, be a new one, absolutely untouched), or has the exact same history (otherwise said, be an exact copy, git
history included) as the one used on this firewall.
--------------------------
Initial setup
@ -84,8 +85,8 @@ User Name Username, when using gitlab and ssh, the d
password When using https authentication, choose a password here.
==================================== ===============================================================================
Make sure to push to a "bare" upstream repository, when pressing "Setup/Test Git" the initial commits should be send to
your git server.
Make sure to push to an empty (as in, new and never used) upstream repository, when pressing "Setup/Test Git" the initial
commits should be sent to your git server.
--------------------------
SSH Setup