Send archive back to git -archive
gitupload -archive <directory>
" 1." 4.2 Clients may request a commit or tree that is pointed to directly by a ref . E .g ., gitarchive --remote=origin v1 .0 . '-04' 2. '+01' .sp -1
" 2." 4.2 Clients may request a sub -tree within a commit or tree using the ref:path syntax . E .g ., gitarchive --remote=origin v1 .0:Documentation . '-04' 3. '+01' .sp -1
" 3." 4.2 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 gitarchive --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 .
<directory> The repository to get a tar archive from .