Skip to content

Commit 1c953c9

Browse files
committed
doc: git-push: update intro
- Avoid unnecessary jargon ("refs") - Move down the reference to hooks, it's less important than the command's basic usage Signed-off-by: Julia Evans <[email protected]>
1 parent c44beea commit 1c953c9

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

Documentation/git-push.adoc

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -19,12 +19,8 @@ SYNOPSIS
1919
DESCRIPTION
2020
-----------
2121

22-
Updates remote refs using local refs, while sending objects
23-
necessary to complete the given refs.
24-
25-
You can make interesting things happen to a repository
26-
every time you push into it, by setting up 'hooks' there. See
27-
documentation for linkgit:git-receive-pack[1].
22+
Updates one or more branches, tags, or other references in a remote
23+
repository from your local repository.
2824

2925
When the command line does not specify where to push with the
3026
`<repository>` argument, `branch.*.remote` configuration for the
@@ -44,6 +40,9 @@ corresponding upstream branch, but as a safety measure, the push is
4440
aborted if the upstream branch does not have the same name as the
4541
local one.
4642

43+
You can make interesting things happen to a repository
44+
every time you push into it, by setting up 'hooks' there. See
45+
documentation for linkgit:git-receive-pack[1].
4746

4847
OPTIONS[[OPTIONS]]
4948
------------------

0 commit comments

Comments
 (0)