git-upload-archive(1) [osx man page]

GIT-UPLOAD-ARCHIVE(1)						    Git Manual						     GIT-UPLOAD-ARCHIVE(1)

NAME

       git-upload-archive - Send archive back to git-archive

SYNOPSIS

       git upload-archive <directory>

DESCRIPTION

       Invoked by git archive --remote and sends a generated archive to the other end over the Git protocol.

       This command is usually not invoked directly by the end user. The UI for the protocol is on the git archive side, and the program pair is
       meant to be used to get an archive from a remote repository.

SECURITY

       In order to protect the privacy of objects that have been removed from history but may not yet have been pruned, git-upload-archive avoids
       serving archives for commits and trees that are not reachable from the repository's refs. However, because calculating object reachability
       is computationally expensive, git-upload-archive implements a stricter but easier-to-check set of rules:

	1. Clients may request a commit or tree that is pointed to directly by a ref. E.g., git archive --remote=origin v1.0.

	2. Clients may request a sub-tree within a commit or tree using the ref:path syntax. E.g., git archive --remote=origin v1.0:Documentation.

	3. Clients may not use other sha1 expressions, even if the end result is reachable. E.g., neither a relative commit like master^ nor a
	   literal sha1 like abcd1234 is allowed, even if the result is reachable from the refs.

       Note that rule 3 disallows many cases that do not have any privacy implications. These rules are subject to change in future versions of
       git, and the server accessed by git archive --remote may or may not follow these exact rules.

       If the config option uploadArchive.allowUnreachable is true, these rules are ignored, and clients may use arbitrary sha1 expressions. This
       is useful if you do not care about the privacy of unreachable objects, or if your object database is already publicly available for access
       via non-smart-http.

OPTIONS

       <directory>
	   The repository to get a tar archive from.

GIT

       Part of the git(1) suite

Git 2.17.1							    10/05/2018						     GIT-UPLOAD-ARCHIVE(1)

Check Out this Related Man Page

GIT-REMOTE-FD(1)						    Git Manual							  GIT-REMOTE-FD(1)

NAME

       git-remote-fd - Reflect smart transport stream back to caller

SYNOPSIS

       "fd::<infd>[,<outfd>][/<anything>]" (as URL)

DESCRIPTION

       This helper uses specified file descriptors to connect to a remote Git server. This is not meant for end users but for programs and scripts
       calling git fetch, push or archive.

       If only <infd> is given, it is assumed to be a bidirectional socket connected to remote Git server (git-upload-pack, git-receive-pack or
       git-upload-archive). If both <infd> and <outfd> are given, they are assumed to be pipes connected to a remote Git server (<infd> being the
       inbound pipe and <outfd> being the outbound pipe.

       It is assumed that any handshaking procedures have already been completed (such as sending service request for git://) before this helper
       is started.

       <anything> can be any string. It is ignored. It is meant for providing information to user in the URL in case that URL is displayed in some
       context.

ENVIRONMENT VARIABLES

       GIT_TRANSLOOP_DEBUG
	   If set, prints debugging information about various reads/writes.

EXAMPLES

       git fetch fd::17 master
	   Fetch master, using file descriptor #17 to communicate with git-upload-pack.

       git fetch fd::17/foo master
	   Same as above.

       git push fd::7,8 master (as URL)
	   Push master, using file descriptor #7 to read data from git-receive-pack and file descriptor #8 to write data to same service.

       git push fd::7,8/bar master
	   Same as above.

SEE ALSO

       gitremote-helpers(1)

GIT

       Part of the git(1) suite

Git 2.17.1							    10/05/2018							  GIT-REMOTE-FD(1)

Linux and UNIX Man Pages

git-upload-archive(1) [osx man page]

Check Out this Related Man Page