Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Newer
Older
100644 121 lines (88 sloc) 3.691 kb
2a245013 »
2005-07-14 [PATCH] Documentation: send/receive.
1 git-send-pack(1)
2 ================
3
4 NAME
5 ----
3dff5379 »
2007-02-03 Assorted typo fixes
6 git-send-pack - Push objects over git protocol to another repository
2a245013 »
2005-07-14 [PATCH] Documentation: send/receive.
7
8
9 SYNOPSIS
10 --------
7791a1d9 »
2011-07-01 Documentation: use [verse] for SYNOPSIS sections
11 [verse]
5a277f3f »
2011-09-06 Revert "Merge branch 'cb/maint-quiet-push' into maint"
12 'git send-pack' [--all] [--dry-run] [--force] [--receive-pack=<git-receive-pack>] [--verbose] [--thin] [<host>:]<directory> [<ref>...]
2a245013 »
2005-07-14 [PATCH] Documentation: send/receive.
13
14 DESCRIPTION
15 -----------
0b444cdb »
2010-01-10 Documentation: spell 'git cmd' without dash throughout
16 Usually you would want to use 'git push', which is a
483bc4f0 »
2008-06-30 Documentation formatting and cleanup
17 higher-level wrapper of this command, instead. See linkgit:git-push[1].
5cb545fa »
2007-01-17 Documentation: suggest corresponding Porcelain-level in plumbing docs.
18
ba020ef5 »
2008-07-03 manpages: italicize git command names (which were in teletype font)
19 Invokes 'git-receive-pack' on a possibly remote repository, and
ab9b3138 »
2005-08-24 Documentation: multi-head fetch.
20 updates it from the current repository, sending named refs.
2a245013 »
2005-07-14 [PATCH] Documentation: send/receive.
21
22
23 OPTIONS
24 -------
3240240f »
2008-06-08 Docs: Use "-l::\n--long\n" format in OPTIONS sections
25 --receive-pack=<git-receive-pack>::
ba020ef5 »
2008-07-03 manpages: italicize git command names (which were in teletype font)
26 Path to the 'git-receive-pack' program on the remote
2a245013 »
2005-07-14 [PATCH] Documentation: send/receive.
27 end. Sometimes useful when pushing to a remote
28 repository over ssh, and you do not have the program in
29 a directory on the default $PATH.
30
3240240f »
2008-06-08 Docs: Use "-l::\n--long\n" format in OPTIONS sections
31 --exec=<git-receive-pack>::
d23842fd »
2007-01-19 rename --exec to --receive-pack for push and send-pack
32 Same as \--receive-pack=<git-receive-pack>.
33
3240240f »
2008-06-08 Docs: Use "-l::\n--long\n" format in OPTIONS sections
34 --all::
9553d20b »
2005-08-03 git-send-pack: documentation
35 Instead of explicitly specifying which refs to update,
5c633a4c »
2007-09-18 git-push: documentation and tests for pushing only branches
36 update all heads that locally exist.
9553d20b »
2005-08-03 git-send-pack: documentation
37
3240240f »
2008-06-08 Docs: Use "-l::\n--long\n" format in OPTIONS sections
38 --dry-run::
a63103ae »
2007-10-11 Add a --dry-run option to git-send-pack.
39 Do everything except actually send the updates.
40
3240240f »
2008-06-08 Docs: Use "-l::\n--long\n" format in OPTIONS sections
41 --force::
ab9b3138 »
2005-08-24 Documentation: multi-head fetch.
42 Usually, the command refuses to update a remote ref that
43 is not an ancestor of the local ref used to overwrite it.
44 This flag disables the check. What this means is that
45 the remote repository can lose commits; use it with
46 care.
47
3240240f »
2008-06-08 Docs: Use "-l::\n--long\n" format in OPTIONS sections
48 --verbose::
18bd8821 »
2007-01-19 Update documentation of fetch-pack, push and send-pack
49 Run verbosely.
50
3240240f »
2008-06-08 Docs: Use "-l::\n--long\n" format in OPTIONS sections
51 --thin::
738820a9 »
2010-02-18 Documentation: describe --thin more accurately
52 Send a "thin" pack, which records objects in deltified form based
53 on objects not included in the pack to reduce network traffic.
18bd8821 »
2007-01-19 Update documentation of fetch-pack, push and send-pack
54
2a245013 »
2005-07-14 [PATCH] Documentation: send/receive.
55 <host>::
56 A remote host to house the repository. When this
ba020ef5 »
2008-07-03 manpages: italicize git command names (which were in teletype font)
57 part is specified, 'git-receive-pack' is invoked via
2a245013 »
2005-07-14 [PATCH] Documentation: send/receive.
58 ssh.
59
60 <directory>::
61 The repository to update.
62
23bed43d »
2006-10-12 Documentation: add missing second colons and remove a typo
63 <ref>...::
9553d20b »
2005-08-03 git-send-pack: documentation
64 The remote refs to update.
65
66
67 Specifying the Refs
68 -------------------
69
70 There are three ways to specify which refs to update on the
71 remote end.
72
abda1ef5 »
2006-06-03 Documentation: Spelling fixes
73 With '--all' flag, all refs that exist locally are transferred to
ab9b3138 »
2005-08-24 Documentation: multi-head fetch.
74 the remote side. You cannot specify any '<ref>' if you use
9553d20b »
2005-08-03 git-send-pack: documentation
75 this flag.
76
5c633a4c »
2007-09-18 git-push: documentation and tests for pushing only branches
77 Without '--all' and without any '<ref>', the heads that exist
9553d20b »
2005-08-03 git-send-pack: documentation
78 both on the local side and on the remote side are updated.
79
df8baa42 »
2005-10-03 [PATCH] Random documentation fixes
80 When one or more '<ref>' are specified explicitly, it can be either a
9553d20b »
2005-08-03 git-send-pack: documentation
81 single pattern, or a pair of such pattern separated by a colon
df8baa42 »
2005-10-03 [PATCH] Random documentation fixes
82 ":" (this means that a ref name cannot have a colon in it). A
9553d20b »
2005-08-03 git-send-pack: documentation
83 single pattern '<name>' is just a shorthand for '<name>:<name>'.
ab9b3138 »
2005-08-24 Documentation: multi-head fetch.
84
9553d20b »
2005-08-03 git-send-pack: documentation
85 Each pattern pair consists of the source side (before the colon)
ab9b3138 »
2005-08-24 Documentation: multi-head fetch.
86 and the destination side (after the colon). The ref to be
9553d20b »
2005-08-03 git-send-pack: documentation
87 pushed is determined by finding a match that matches the source
88 side, and where it is pushed is determined by using the
ae36bdcf »
2007-11-11 push: use same rules as git-rev-parse to resolve refspecs
89 destination side. The rules used to match a ref are the same
0b444cdb »
2010-01-10 Documentation: spell 'git cmd' without dash throughout
90 rules used by 'git rev-parse' to resolve a symbolic ref
483bc4f0 »
2008-06-30 Documentation formatting and cleanup
91 name. See linkgit:git-rev-parse[1].
9553d20b »
2005-08-03 git-send-pack: documentation
92
ab9b3138 »
2005-08-24 Documentation: multi-head fetch.
93 - It is an error if <src> does not match exactly one of the
94 local refs.
9553d20b »
2005-08-03 git-send-pack: documentation
95
96 - It is an error if <dst> matches more than one remote refs.
97
98 - If <dst> does not match any remote ref, either
99
df8baa42 »
2005-10-03 [PATCH] Random documentation fixes
100 * it has to start with "refs/"; <dst> is used as the
9553d20b »
2005-08-03 git-send-pack: documentation
101 destination literally in this case.
102
df8baa42 »
2005-10-03 [PATCH] Random documentation fixes
103 * <src> == <dst> and the ref that matched the <src> must not
9553d20b »
2005-08-03 git-send-pack: documentation
104 exist in the set of remote refs; the ref matched <src>
105 locally is used as the name of the destination.
106
ab9b3138 »
2005-08-24 Documentation: multi-head fetch.
107 Without '--force', the <src> ref is stored at the remote only if
108 <dst> does not exist, or <dst> is a proper subset (i.e. an
a75d7b54 »
2009-10-24 Use 'fast-forward' all over the place
109 ancestor) of <src>. This check, known as "fast-forward check",
ab9b3138 »
2005-08-24 Documentation: multi-head fetch.
110 is performed in order to avoid accidentally overwriting the
111 remote ref and lose other peoples' commits from there.
112
a75d7b54 »
2009-10-24 Use 'fast-forward' all over the place
113 With '--force', the fast-forward check is disabled for all refs.
ab9b3138 »
2005-08-24 Documentation: multi-head fetch.
114
115 Optionally, a <ref> parameter can be prefixed with a plus '+' sign
116 to disable the fast-forward check only on that ref.
117
2a245013 »
2005-07-14 [PATCH] Documentation: send/receive.
118 GIT
119 ---
9e1f0a85 »
2008-06-06 documentation: move git(7) to git(1)
120 Part of the linkgit:git[1] suite
Something went wrong with that request. Please try again.