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

[PATCH] Documentation: quote braces in {upstream} notation

From
Thomas Rast <trast@student.ethz.ch>
Date
Feb 10, 2010, 16:30 UTC
Message-ID
<a91746a91d0ad0b38a4e49f1f79a056a2d3eac69.1265819421.git.trast@student.ethz.ch>
The lack of quoting made the entire line disappear.
Signed-off-by: Thomas Rast <trast@student.ethz.ch>
---
 Documentation/git-rev-parse.txt |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt
index fc73152..d677c72 100644
--- a/Documentation/git-rev-parse.txt
+++ b/Documentation/git-rev-parse.txt
@@ -244,7 +244,7 @@ when you run 'git merge'.
 * The special construct '@\{-<n>\}' means the <n>th branch checked out
   before the current one.
 
-* The suffix '@{upstream}' to a ref (short form 'ref@{u}') refers to
+* The suffix '@\{upstream\}' to a ref (short form 'ref@\{u\}') refers to
   the branch the ref is set to build on top of.  Missing ref defaults
   to the current branch.
 
-- 
1.7.0.rc2.178.g109e1
Next: Junio C Hamano
Message 1 of 2 in “Documentation: quote braces in {upstream} notation”
  1. Documentation: quote braces in {upstream} notationThomas Rast, Feb 10, 2010
  2. Junio C HamanoFeb 10, 2010

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.