From: Jeff King <email@example.com> To: "brian m. carlson" <firstname.lastname@example.org> Cc: Mark Florian <email@example.com>, firstname.lastname@example.org Subject: Re: `@` alias for `HEAD` not working in `git push -u origin @` Date: Wed, 31 Jul 2019 01:58:33 -0400 [thread overview] Message-ID: <20190731055832.GA18039@sigill.intra.peff.net> (raw) In-Reply-To: <20190710233937.GG9224@genre.crustytoothpaste.net> On Wed, Jul 10, 2019 at 11:39:37PM +0000, brian m. carlson wrote: > 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 > destination. > > 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/ I see I was cc'd on that original, but I don't remember ever reading it. It seems like a sane enough idea to me. Although I did notice that you mentioned there: > I probably type "git push upstream HEAD" from five to thirty times a > day I find I do that rarely, because I have: [push] default = current and in a triangular workflow, I have: [remote] pushDefault = upstream So "git push" without arguments typically does the same thing for me. Not an argument against your patch, but just something you might find useful. -Peff
next prev parent reply other threads:[~2019-07-31 5:58 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 2019-07-11 14:48 ` brian m. carlson 2019-07-12 10:29 ` Johannes Schindelin 2019-07-31 5:58 ` Jeff King [this message] 2019-07-31 16:10 ` Junio C Hamano
Reply instructions: 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: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style 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 \ --in-reply-to=20190731055832.GA18039@sigill.intra.peff.net \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: `@` alias for `HEAD` not working in `git push -u origin @`' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * 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: https://80x24.org/mirrors/git.git 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).