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

[PATCH 3/7] Documentation: rework SHA1 description in git push

From
AMAnders Melchiorsen <mail@cup.kalibalik.dk>
Date
Oct 29, 2008, 20:25 UTC
Message-ID
<1225311945-17100-4-git-send-email-mail@cup.kalibalik.dk>
In-Reply-To
<1225311945-17100-3-git-send-email-mail@cup.kalibalik.dk>

Get rid of a double pair of parentheses. The arbitrary SHA1 is a special case, so it can be postponed a bit.

Also mention HEAD, which is possibly the most useful SHA1 in this situation.

Mention that a SHA1 cannot be automatically matched to a <dst>.
Add HEAD as an example of an arbitrary SHA1.
Signed-off-by: Anders Melchiorsen <mail@cup.kalibalik.dk>
---
 Documentation/git-push.txt |   12 +++++++++---
 1 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index 02c7dae..fb9fb97 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -38,9 +38,7 @@ OPTIONS
 	by the source ref, followed by a colon `:`, followed by
 	the destination ref.
 +
-The <src> side represents the source branch (or arbitrary
-"SHA1 expression", such as `master~4` (four parents before the
-tip of `master` branch); see linkgit:git-rev-parse[1]) that you
+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
@@ -63,6 +61,10 @@ the local side, the remote side is updated if a head of the same name
 already exists on the remote side.  This is the default operation mode
 if no explicit refspec is found (that is neither on the command line
 nor in any Push line of the corresponding remotes file---see below).
++
+The <src> can be an arbitrary "SHA1 expression", such as `HEAD`
+or `master~4` (see linkgit:git-rev-parse[1]). In this case, a
+<dst> location has to be named.
 
 --all::
 	Instead of naming each ref to push, specifies that all
@@ -193,6 +195,10 @@ git push origin master::
 	with it.  If `master` did not exist remotely, it would be
 	created.
 
+git push origin HEAD:master::
+	Push the current head to the remote ref matching `master` in
+	the `origin` repository.
+
 git push origin :experimental::
 	Find a ref that matches `experimental` in the `origin` repository
 	(e.g. `refs/heads/experimental`), and delete it.
-- 
1.6.0.2.514.g23abd3
Previous: Anders MelchiorsenNext: Anders Melchiorsen
Message 4 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.