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)

GIT-TAR-TREE(1) 						    Git Manual							   GIT-TAR-TREE(1)

NAME

       git-tar-tree - Create a tar archive of the files in the named tree object

SYNOPSIS

       git tar-tree [--remote=<repo>] <tree-ish> [ <base> ]

DESCRIPTION

       THIS COMMAND IS DEPRECATED. Use git archive with --format=tar option instead (and move the <base> argument to --prefix=base/).

       Creates a tar archive containing the tree structure for the named tree. When <base> is specified it is added as a leading path to the files
       in the generated tar archive.

       git tar-tree behaves differently when given a tree ID versus when given a commit ID or tag ID. In the first case the current time is used
       as modification time of each file in the archive. In the latter case the commit time as recorded in the referenced commit object is used
       instead. Additionally the commit ID is stored in a global extended pax header. It can be extracted using git get-tar-commit-id.

OPTIONS

       <tree-ish>
	   The tree or commit to produce tar archive for. If it is the object name of a commit object.

       <base>
	   Leading path to the files in the resulting tar archive.

       --remote=<repo>
	   Instead of making a tar archive from local repository, retrieve a tar archive from a remote repository.

CONFIGURATION

       tar.umask
	   This variable can be used to restrict the permission bits of tar archive entries. The default is 0002, which turns off the world write
	   bit. The special value "user" indicates that the archiving user's umask will be used instead. See umask(2) for details.

EXAMPLES

       git tar-tree HEAD junk | (cd /var/tmp/ && tar xf -)
	   Create a tar archive that contains the contents of the latest commit on the current branch, and extracts it in /var/tmp/junk directory.

       git tar-tree v1.4.0 git-1.4.0 | gzip >git-1.4.0.tar.gz
	   Create a tarball for v1.4.0 release.

       git tar-tree v1.4.0^{tree} git-1.4.0 | gzip >git-1.4.0.tar.gz
	   Create a tarball for v1.4.0 release, but without a global extended pax header.

       git tar-tree --remote=example.com:git.git v1.4.0 >git-1.4.0.tar
	   Get a tarball v1.4.0 from example.com.

       git tar-tree HEAD:Documentation/ git-docs > git-1.4.0-docs.tar
	   Put everything in the current head's Documentation/ directory into git-1.4.0-docs.tar, with the prefix git-docs/.

GIT

       Part of the git(1) suite

Git 1.8.3.1							    06/10/2014							   GIT-TAR-TREE(1)