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

Re: [PATCH] rev-parse: Clarify documentation of @{upstream} syntax

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Mar 17, 2013, 04:31 UTC
Message-ID
<CAPig+cTL_u_AV1-E9JhBRP2JP97vod9iWpRtM0SETX9-GL_-2w@mail.gmail.com>
In-Reply-To
<1363459903-32358-1-git-send-email-draenog@pld-linux.org>
On Sat, Mar 16, 2013 at 2:51 PM, Kacper Kornet <draenog@pld-linux.org> wrote:
Show 5 quoted lines
> git-rev-parse interprets string in string@{upstream} as a name of
> a branch not a ref. For example refs/heads/master@{upstream} looks
> for an upstream branch that is merged by git-pull to ref
> refs/heads/refs/heads/master not to refs/heads/master. However the
> documentation could misled a user to believe that the string is
s/misled/mislead/
> interpreted as ref.
Previous: Kacper KornetNext: Kacper Kornet
Message 2 of 3 in “rev-parse: Clarify documentation of @{upstream} syntax”
  1. rev-parse: Clarify documentation of @{upstream} syntaxKacper Kornet, Mar 16, 2013
  2. Eric SunshineMar 17, 2013
  3. t1507: Test that branchname@{upstream} is interpreted as branchKacper Kornet, Mar 17, 2013

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.