From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "brian m. carlson" <email@example.com>
Cc: Mark Florian <firstname.lastname@example.org>, email@example.com
Subject: Re: `@` alias for `HEAD` not working in `git push -u origin @`
Date: Thu, 11 Jul 2019 11:46:26 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.firstname.lastname@example.org> (raw)
On Wed, 10 Jul 2019, brian m. carlson wrote:
> On 2019-07-10 at 05:06:08, Mark Florian wrote:
> > I learned today that `@` is a shortcut for `HEAD`. From `git help reivisions`:
> > @ alone is a shortcut for HEAD.
> > However, when I tried to use it in a command I frequently use, I got an error:
> > $ git push -u origin @
> > fatal: invalid refspec '@'
> > I'm running git version 2.22.0 on Linux.
> > Is this a bug, or have I misunderstood how this is supposed to work?
> This is a bug. If the destination side of a refspec is omitted, and the
> source side resolves to a ref starting with "refs/heads/" or
> "refs/tags/" (which I expect it does here), then that ref is used as the
> I submitted a patch at , but it was decided not to pick it up. If
> Junio and the list decide that it's wanted, I'm happy to resend or
> revise and resend.
>  https://email@example.com/
After reading that thread, I come to the conclusion that it was not so
much a decision not to pick it up, but more like a falling between the
I would be in favor of this patch.
Since I have your attention and since I am interested in a related issue
(when I wanted to propose a GSoC mini project to let `git fetch <remote>
@` expand the `@` to the current (local) branch name, Matthieu Moy
pointed out that `git fetch --current <remote>` might be a better UI):
what does your patch do with `git fetch`'s refspec arguments?
next prev parent reply other threads:[~2019-07-11 9:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 5:06 Mark Florian
2019-07-10 23:39 ` brian m. carlson
2019-07-11 9:46 ` Johannes Schindelin [this message]
2019-07-11 14:48 ` brian m. carlson
2019-07-12 10:29 ` Johannes Schindelin
2019-07-31 5:58 ` Jeff King
2019-07-31 16:10 ` Junio C Hamano
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: `@` alias for `HEAD` not working in `git push -u origin @`' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox:
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).