ID: 45aa89a8ff044d280af329e0bc823c371d5aa738
76 lines
—
2K —
View raw
| General usage
-------------------------------------------------------------------------------
# List of available commands over SSH
ssh git@example.org help
# List of user repositories and access permissions
ssh git@example.org info
Repositories
-------------------------------------------------------------------------------
# Cloning a repository anonymously
git clone https://example.org/repository.git
# Cloning a repository as registered users
git clone git@example.org:repository
# Creating a new repository
Either clone, or push to, a nonexistent repository. It will be initiated automatically
as long as the user has write permission.
git clone git@example.org:repository
git push git@example.org:repository master
# Set repository description
ssh git@example.org desc <repositoy> "<description>"
# Pushing to a repository
git push git@example.org:repository.git
# Change default branch by repoint HEAD to other branches
ssh git@example.org symbolic-ref repository.git HEAD refs/heads/main
# Delete repository (D command)
ssh git@example.org D unlock <repository>
ssh git@example.org D rm <repository>
Mailing lists
-------------------------------------------------------------------------------
Mailing lists are where collaboration happens, and they are stored in repositories
too.
# Create a new mailing list
Create a new repository with the suffix ".mlist":
git clone git@example.org:project.mlist
CLIF will then begin accepting emails for project@example.org and store them
inside the "project.mlist" repository.
# New threads
New threads are created simply by sending a new email to the list address. An account
is not required for starting new threads and participating in discussions.
# Join an existing thread
It is possible to join an existing thread by sending an email containing the header
"In-Reply-To: <Message-ID>", where <Message-ID> is the ID value of any previous message.
|