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

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

From
AMAnders Melchiorsen <mail@cup.kalibalik.dk>
Date
Oct 29, 2008, 20:25 UTC
Message-ID
<1225311945-17100-5-git-send-email-mail@cup.kalibalik.dk>
In-Reply-To
<1225311945-17100-4-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 fb9fb97..9788d49 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -42,8 +42,7 @@ The <src> side represents the source branch 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 5 of 15 in “Some updates to refspec documentation”
  1. Anders MelchiorsenOct 29, 2008
  2. 1/7 Documentation: do not use regexp in refspec descriptionsAnders Melchiorsen, Oct 29, 2008
  3. 2/7 Documentation: git push repository can also be a remoteAnders Melchiorsen, Oct 29, 2008
  4. 3/7 Documentation: rework SHA1 description in git pushAnders Melchiorsen, Oct 29, 2008
  5. 4/7 Documentation: remove a redundant elaborationAnders Melchiorsen, Oct 29, 2008
  6. 5/7 Documentation: elaborate on pushing tagsAnders Melchiorsen, Oct 29, 2008
  7. 6/7 Documentation: mention branches rather than headsAnders Melchiorsen, Oct 29, 2008
  8. 7/7 Documentation: avoid using undefined parametersAnders Melchiorsen, Oct 29, 2008
  9. Daniel BarkalowOct 29, 2008
  10. Junio C HamanoOct 31, 2008
  11. Anders MelchiorsenNov 2, 2008
  12. Junio C HamanoOct 31, 2008
  13. Anders MelchiorsenNov 2, 2008
  14. Anders MelchiorsenOct 29, 2008
  15. Anders MelchiorsenOct 29, 2008

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.