From: Eric Sunshine <sunshine@sunshineco.com>
Date: Sun, 17 Mar 2013 04:31:18 GMT
Subject: Re: [PATCH] rev-parse: Clarify documentation of @{upstream} syntax
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:
> 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.