git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 2/4] Documentation: remove a redundant elaboration

From
AMAnders Melchiorsen <mail@cup.kalibalik.dk>
Date
Jan 18, 2009, 14:36 UTC
Message-ID
<1232289418-25627-3-git-send-email-mail@cup.kalibalik.dk>
In-Reply-To
<1232289418-25627-2-git-send-email-mail@cup.kalibalik.dk>

The comment in parentheses is wrong, as one has to leave out both the colon and <dst>. This situation is covered by the section a few lines down:

  A parameter <ref> without a colon pushes the <ref> from the source
  repository to the destination repository under the same name.
So, just remove the parentheses.
Signed-off-by: Anders Melchiorsen <mail@cup.kalibalik.dk>
---
 Documentation/git-push.txt |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index 8bfa7cb..6d3c711 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -44,8 +44,7 @@ tip of `master` branch); see linkgit:git-rev-parse[1]) that you
 want to push.  The <dst> side represents the destination location.
 +
 The local ref that matches <src> is used
-to fast forward the remote ref that matches <dst> (or, if no <dst> was
-specified, the same ref that <src> referred to locally).  If
+to fast forward the remote ref that matches <dst>.  If
 the optional leading plus `+` is used, the remote ref is updated
 even if it does not result in a fast forward update.
 +
-- 
1.6.0.2.514.g23abd3
Previous: Anders MelchiorsenNext: Anders Melchiorsen
Message 3 of 6 in “Clarifying the refspec documentation”
  1. 0/4 Clarifying the refspec documentationAnders Melchiorsen, Jan 18, 2009
  2. 1/4 Documentation: git push repository can also be a remoteAnders Melchiorsen, Jan 18, 2009
  3. 2/4 Documentation: remove a redundant elaborationAnders Melchiorsen, Jan 18, 2009
  4. 3/4 Documentation: mention branches rather than headsAnders Melchiorsen, Jan 18, 2009
  5. 4/4 Documentation: avoid using undefined parametersAnders Melchiorsen, Jan 18, 2009
  6. Junio C HamanoJan 19, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.