git-request-pull

Produce a request summarizing the changes between the v1.1 release and a specified branch

$ git request-pull [v1.1] [https://example.com/project] [branch_name]

$ git request-pull [v0.1] [https://example.com/project] [foo:bar]

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

git request-pull creates a human-readable summary of changes between commits, formatted for emailing to project maintainers. It highlights new commits reachable from an optional <end> commit (default: HEAD) but not present in the upstream repository at <url> (default branch: HEAD), starting from <start> commit.

The output includes:
• A suggested git pull command.
• Short log of new commits with titles and authors.
• The provided URL for context.

Ideal for email-based workflows like Linux kernel development, where contributors request pulls via mailing lists. It fetches refs from <url> to determine missing commits, ensuring only relevant changes are listed. Does not send email—use with git send-email or git format-patch.

Limited to text summary; no patches included. Assumes <url> is cloneable and <start> exists upstream.

Requires network access to <url>; fails if unreachable. Lists commits based on HEAD unless specified—branch mismatches may include extras. Not for large histories (slow, verbose). Obsolete for GitHub/GitLab; use web PRs instead. No options for customization.

git request-pull v2.30.0 https://github.com/git/git.git
Generates summary from v2.30.0 to HEAD for emailing Git maintainers.

The following changes since commit <start> are available:

John Doe (3):
commit1
commit2
commit3

<url> (?/?) => v2.31.0
You can fetch these changes with:
git pull https://github.com/user/repo.git <branch>

Added in Git 1.0.rc1 (2005) by Junio C Hamano for kernel-style email pulls. Evolved minimally; remains stable for porcelain use in maintainer workflows.

git-log(1), git-format-patch(1), git-send-email(1), git-fetch(1)