git-request-pull(1) [osx man page]

GIT-REQUEST-PULL(1)						    Git Manual						       GIT-REQUEST-PULL(1)

NAME

       git-request-pull - Generates a summary of pending changes

SYNOPSIS

       git request-pull [-p] <start> <url> [<end>]

DESCRIPTION

       Generate a request asking your upstream project to pull changes into their tree. The request, printed to the standard output, begins with
       the branch description, summarizes the changes and indicates from where they can be pulled.

       The upstream project is expected to have the commit named by <start> and the output asks it to integrate the changes you made since that
       commit, up to the commit named by <end>, by visiting the repository named by <url>.

OPTIONS

       -p
	   Include patch text in the output.

       <start>
	   Commit to start at. This names a commit that is already in the upstream history.

       <url>
	   The repository URL to be pulled from.

       <end>
	   Commit to end at (defaults to HEAD). This names the commit at the tip of the history you are asking to be pulled.

	   When the repository named by <url> has the commit at a tip of a ref that is different from the ref you have locally, you can use the
	   <local>:<remote> syntax, to have its local name, a colon :, and its remote name.

EXAMPLE

       Imagine that you built your work on your master branch on top of the v1.0 release, and want it to be integrated to the project. First you
       push that change to your public repository for others to see:

	   git push https://git.ko.xz/project master

       Then, you run this command:

	   git request-pull v1.0 https://git.ko.xz/project master

       which will produce a request to the upstream, summarizing the changes between the v1.0 release and your master, to pull it from your public
       repository.

       If you pushed your change to a branch whose name is different from the one you have locally, e.g.

	   git push https://git.ko.xz/project master:for-linus

       then you can ask that to be pulled with

	   git request-pull v1.0 https://git.ko.xz/project master:for-linus

GIT

       Part of the git(1) suite

Git 2.17.1							    10/05/2018						       GIT-REQUEST-PULL(1)

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)