freshlybakedca.ke / git
Git fork
fork atom

doc: git-push: clarify intro

From user feedback, 5 users are unsure what "ref" and/or "objects" means
in this context. 3 users said they don't know what "complete the refs"
means.

Many users also commented that receive hooks do not seem like the most
important thing to know about `git push`, and that this information
should not be the second sentence in the man page.

Use more familiar language to make it more accessible to users who do
not know what a "ref" is and move the "hooks" comment to the end.

Signed-off-by: Julia Evans <julia@jvns.ca>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

authored by

Julia Evans and committed by
Junio C Hamano 5b696cb3 92c87bdc

+7 -6
unified split
+7 -6
Documentation/git-push.adoc
··· 19 19 DESCRIPTION 20 20 ----------- 21 21 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, and sends all necessary data 24 + that isn't already on the remote. 28 25 29 26 When the command line does not specify where to push with the 30 27 `<repository>` argument, `branch.*.remote` configuration for the ··· 43 40 corresponding upstream branch, but as a safety measure, the push is 44 41 aborted if the upstream branch does not have the same name as the 45 42 local one. 43 + 44 + You can make interesting things happen to a repository 45 + every time you push into it, by setting up 'hooks' there. See 46 + documentation for linkgit:git-receive-pack[1]. 46 47 47 48 48 49 OPTIONS[[OPTIONS]]