From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: [9front] Fwd: [9front-commits] ori: hg/plan9front: git: got git?
Date: Mon, 17 May 2021 01:13:10 -0400 [thread overview]
Message-ID: <369A65E4-CFFE-4BE9-83E8-1F7E41905B32@stanleylieber.com> (raw)
In-Reply-To: <hg.d48388affe2e.1621216231.4892889753185008284@code.9front.org>
right on.
sl
-------- Original Message --------
From: The Computer <commits@code.9front.org>
Sent: May 16, 2021 9:50:31 PM EDT
To: 9front-commits@9front.org
Subject: [9front-commits] ori: hg/plan9front: git: got git?
details: http://code.9front.org/hg/plan9front/rev/d48388affe2e
changeset: 8459:d48388affe2e
user: Ori Bernstein <ori@eigenstate.org>
date: Sun May 16 18:49:45 2021 -0700
description: git: got git?
Add a snapshot of git9 to 9front.
diffstat:
sys/man/1/git | 643 +++++++++++++++++
sys/man/4/gitfs | 112 +++
sys/src/cmd/git/add | 39 +
sys/src/cmd/git/branch | 109 ++
sys/src/cmd/git/clone | 115 +++
sys/src/cmd/git/commit | 150 ++++
sys/src/cmd/git/compat | 158 ++++
sys/src/cmd/git/conf.c | 97 ++
sys/src/cmd/git/delta.c | 219 +++++
sys/src/cmd/git/diff | 37 +
sys/src/cmd/git/export | 89 ++
sys/src/cmd/git/fetch.c | 316 ++++++++
sys/src/cmd/git/fs.c | 853 ++++++++++++++++++++++
sys/src/cmd/git/git.h | 303 ++++++++
sys/src/cmd/git/import | 99 ++
sys/src/cmd/git/init | 38 +
sys/src/cmd/git/log.c | 329 ++++++++
sys/src/cmd/git/merge | 47 +
sys/src/cmd/git/mkfile | 57 +
sys/src/cmd/git/objset.c | 67 +
sys/src/cmd/git/ols.c | 170 ++++
sys/src/cmd/git/pack.c | 1712 ++++++++++++++++++++++++++++++++++++++++++++++
sys/src/cmd/git/proto.c | 459 ++++++++++++
sys/src/cmd/git/pull | 82 ++
sys/src/cmd/git/push | 51 +
sys/src/cmd/git/query.c | 196 +++++
sys/src/cmd/git/rebase | 92 ++
sys/src/cmd/git/ref.c | 677 ++++++++++++++++++
sys/src/cmd/git/repack.c | 85 ++
sys/src/cmd/git/revert | 19 +
sys/src/cmd/git/rm | 3 +
sys/src/cmd/git/save.c | 401 ++++++++++
sys/src/cmd/git/send.c | 272 +++++++
sys/src/cmd/git/serve.c | 558 ++++++++++++++
sys/src/cmd/git/util.c | 321 ++++++++
sys/src/cmd/git/walk.c | 333 ++++++++
36 files changed, 9308 insertions(+), 0 deletions(-)
diffs (truncated from 9488 to 300 lines):
diff --git a/sys/man/1/git b/sys/man/1/git
new file mode 100644
--- /dev/null
+++ b/sys/man/1/git
@@ -0,0 +1,643 @@
+.TH GIT 1
+.SH NAME
+git, git/conf, git/query, git/walk, git/clone, git/branch,
+git/commit, git/diff, git/init, git/log, git/merge, git/push,
+git/pull, git/rm, git/serve
+\- Manage git repositories.
+
+.SH SYNOPSIS
+.PP
+.B git/add
+[
+.B -r
+]
+.I path...
+.PP
+.B git/rm
+.I path...
+.PP
+.B git/branch
+[
+.B -adns
+]
+[
+.B -b
+.I base
+]
+.I newbranch
+.PP
+.B git/clone
+[
+.I remote
+[
+.I local
+]
+]
+.PP
+.B git/commit
+[
+.B -re
+]
+[
+.B -m msg
+]
+[
+.I file...
+]
+.PP
+.B git/compat
+.PP
+.B git/conf
+[
+.B -r
+]
+[
+.B -f
+.I file
+]
+.I keys...
+.PP
+.B git/diff
+[
+.B -c
+.I branch
+]
+[
+.B -s
+]
+[
+.I file...
+]
+.PP
+.B git/revert
+[
+.B -c
+.I commit
+]
+.I file...
+.PP
+.B git/export
+[
+.I commits...
+]
+.PP
+.B git/import
+[
+.I commits...
+]
+.PP
+.B git/init
+[
+.B -b
+]
+[
+.I dir
+]
+[
+.B -u
+.I upstream
+]
+.PP
+.B git/log
+[
+.B -c
+.I commit
+.B | -e
+.I expr
+]
+[
+.B -s
+]
+[
+.I files...
+]
+.PP
+.B git/merge
+.I theirs
+.PP
+.B git/rebase
+[
+.B -ari
+]
+[
+.B onto
+]
+.PP
+.B git/pull
+[
+.B -f
+]
+[
+.B -q
+]
+[
+.B -a
+]
+[
+.B -u
+.I upstream
+]
+.PP
+.B git/push
+[
+.B -a
+]
+[
+.B -u
+.I upstream
+]
+[
+.B -b
+.I branch
+]
+[
+.B -r
+.I branch
+]
+.PP
+.B git/serve
+[
+.B -w
+]
+[
+.B -r
+.I path
+]
+.PP
+.B git/query
+[
+.B -pcr
+]
+.I query
+.PP
+.B git/walk
+[
+.B -qc
+]
+[
+.B -b
+.I branch
+]
+[
+.B -f
+.I filters
+]
+[
+.I [files...]
+]
+
+.SH DESCRIPTION
+.PP
+Git is a distributed version control system.
+This means that each repository contains a full copy of the history.
+This history is then synced between computers as needed.
+
+.PP
+These programs provide tools to manage and interoperate with
+repositories hosted in git.
+
+.SH CONCEPTS
+
+Git stores snapshots of the working directory.
+Files can either be in a tracked or untracked state.
+Each commit takes the current version of all tracked files and
+adds them to a new commit.
+
+This history is stored in the
+.I .git
+directory.
+This suite of
+.I git
+tools provides a file interface to the
+.I .git
+directory mounted on
+.I /mnt/git.
+Modifications to the repository are done directly to the
+.I .git
+directory, and are reflected in the file system interface.
+This allows for easy scripting, without excessive complexity
+in the file API.
+
+.SH COMMANDS
+
+.PP
+.B Git/init
+is used to create a new git repository, with no code or commits.
+The repository is created in the current directory by default.
+Passing a directory name will cause the repository to be created
+there instead.
+Passing the
+.B -b
+option will cause the repository to be initialized as a bare repository.
+Passing the
+.B -u
+.I upstream
+option will cause the upstream to be configured to
+.I upstream.
+
+.PP
+.B Git/clone
+will take an existing repository, served over either the
+.I git://
+or
+.I ssh://
+protocols.
+The first argument is the repository to clone.
+The second argument, optionally, specifies the location to clone into.
+If not specified, the repository will be cloned into the last path component
+of the clone source, with the
+.I .git
+stripped off if present.
+
+.PP
+.B Git/push
+is used to push the current changes to a remote repository.
+When no arguments are provided, the remote repository is taken from
+the origin configured in
+.I .git/config,
+and only the changes on the current branch are pushed.
+When passed the
+.I -a
+option, all branches are pushed.
+When passed the
+.I -u upstream
+option, the changed are pushed to
+.I upstream
+instead of the configured origin.
+When given the
+.I -r
+option, the branch is deleted from origin, instead of updated.
+
+.PP
+.B Git/revert
+restores the named files from HEAD. When passed the -c flag, restores files from
+the named commit.
+
+.PP
+.B Git/pull
+behaves in a similar manner to git/push, however it gets changes from
+the upstream repository.
+After fetching, it checks out the changes into the working directory.
+When passed the
+.I -f
+option, the update of the working copy is suppressed.
+When passed the
+.I -u upstream
+option, the changes are pulled from
+.I upstream
+instead of the configured origin.
+
+.PP
+.B Git/serve
+serves repositories using the
+.I git://
+protocol over stdin.
+By default, it serves them read-only.
parent reply other threads:[~2021-05-17 5:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <hg.d48388affe2e.1621216231.4892889753185008284@code.9front.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=369A65E4-CFFE-4BE9-83E8-1F7E41905B32@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).