From: Julia Evans <julia@xxxxxxx> - Users don't understand what a "ref" is, expand it - Remove "complete the given refs" (that phrase is confusing to many users, and it's obvious that pushing a branch involves sending the new code) - Move down the reference to hooks, it's less important than the command's basic usage Signed-off-by: Julia Evans <julia@xxxxxxx> --- Documentation/git-push.adoc | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/Documentation/git-push.adoc b/Documentation/git-push.adoc index d1978650d60a..e73b64f61fd0 100644 --- a/Documentation/git-push.adoc +++ b/Documentation/git-push.adoc @@ -19,12 +19,8 @@ SYNOPSIS DESCRIPTION ----------- -Updates remote refs using local refs, while sending objects -necessary to complete the given refs. - -You can make interesting things happen to a repository -every time you push into it, by setting up 'hooks' there. See -documentation for linkgit:git-receive-pack[1]. +Updates one or more branches, tags, or other references in a remote +repository from your local repository. When the command line does not specify where to push with the `<repository>` argument, `branch.*.remote` configuration for the @@ -44,6 +40,9 @@ corresponding upstream branch, but as a safety measure, the push is aborted if the upstream branch does not have the same name as the local one. +You can make interesting things happen to a repository +every time you push into it, by setting up 'hooks' there. See +documentation for linkgit:git-receive-pack[1]. OPTIONS[[OPTIONS]] ------------------ -- gitgitgadget
