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

Re: push.default documented in "man git-push"?

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Oct 2, 2012, 15:09 UTC
Message-ID
<CALkWK0mxLQNOE8kZUJrxYQMWXpzZW0uS+N2iGXxdRmCXTzYcBQ@mail.gmail.com>
In-Reply-To
<CAN7QDoK4WCuRMu+KV6ACo9miR9_eFEE510J5PDiPk+BXLyQG9Q@mail.gmail.com>
David Glasser wrote:
Show 5 quoted lines
> Is the newish push.default documented in the "git push" manpage
> anywhere? I don't see it mentioned (and there are several references
> to the "default" behavior), but maybe I'm missing something. Is it
> left out on purpose (ie, config values aren't supposed to be mentioned
> in command manpages)?

You're right. It's documented in `man git-config`, but we should probably mention it in the `git-push` manpage.

--8<--
From: Ramkumar Ramachandra <artagnon@gmail.com>
Date: Tue, 2 Oct 2012 20:37:13 +0530
Subject: [PATCH] Documentation: mention `push.default` in git-push.txt
Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
---
 Documentation/git-push.txt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index cb97cc1..8751b38 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -37,7 +37,8 @@ OPTIONS[[OPTIONS]]
        `+`, followed by the source ref <src>, followed
        by a colon `:`, followed by the destination ref <dst>.
        It is used to specify with what <src> object the <dst> ref
-       in the remote repository is to be updated.
+       in the remote repository is to be updated.  If not specified,
+       the configuration variable `push.default` is used.
 +
 The <src> is often the name of the branch you would want to push, but
 it can be any arbitrary "SHA-1 expression", such as `master~4` or
-- 
1.7.12.1.428.g652398a.dirty
Previous: David GlasserNext: David Glasser
Message 2 of 35 in “push.default documented in "man git-push"?”
  1. David GlasserOct 2, 2012
  2. Ramkumar RamachandraOct 2, 2012
  3. David GlasserOct 2, 2012
  4. Ramkumar RamachandraOct 2, 2012
  5. Matthieu MoyOct 2, 2012
  6. Ramkumar RamachandraOct 2, 2012
  7. Junio C HamanoOct 2, 2012
  8. Matthieu MoyOct 2, 2012
  9. Junio C HamanoOct 2, 2012
  10. David GlasserOct 2, 2012
  11. Junio C HamanoOct 2, 2012
  12. Matthieu MoyOct 3, 2012
  13. Ramkumar RamachandraOct 3, 2012
  14. Nguyen Thai Ngoc DuyOct 3, 2012
  15. Ramkumar RamachandraOct 3, 2012
  16. Nguyen Thai Ngoc DuyOct 3, 2012
  17. Ramkumar RamachandraOct 3, 2012
  18. Nguyen Thai Ngoc DuyOct 3, 2012
  19. Junio C HamanoOct 3, 2012
  20. Jeff KingOct 3, 2012
  21. Junio C HamanoOct 8, 2012
  22. Ramkumar RamachandraOct 7, 2012
  23. Junio C HamanoOct 7, 2012
  24. Ramkumar RamachandraOct 8, 2012
  25. Nguyen Thai Ngoc DuyOct 8, 2012
  26. Junio C HamanoOct 3, 2012
  27. Nguyen Thai Ngoc DuyOct 4, 2012
  28. Junio C HamanoOct 4, 2012
  29. Nguyen Thai Ngoc DuyOct 5, 2012
  30. Junio C HamanoOct 5, 2012
  31. Nguyen Thai Ngoc DuyOct 11, 2012
  32. Matthieu MoyOct 11, 2012
  33. Nguyen Thai Ngoc DuyOct 11, 2012
  34. Junio C HamanoOct 11, 2012
  35. Peter KreftingOct 3, 2012

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.