From: Johannes Schindelin <Johannes.Schindelin@gmx.de> 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: Fri, 12 Jul 2019 12:29:06 +0200 (CEST) [thread overview] Message-ID: <nycvar.QRO.email@example.com> (raw) In-Reply-To: <20190711144828.GH9224@genre.crustytoothpaste.net> Hi brian, On Thu, 11 Jul 2019, brian m. carlson wrote: > On 2019-07-11 at 09:46:26, Johannes Schindelin wrote: > > > 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? > > I haven't checked. I believe it would resolve "git fetch origin @" to > "git fetch origin HEAD" and "git fetch origin @:refs/heads/master" to > "git fetch origin HEAD:refs/heads/master". That sounds like a sane behavior, as `@` on the "src" side of a refspec that tries to fetch from a remote repository should probably not expand to a _local_ branch. > I can add some additional tests for this case, although I'm not > especially sure that it provides useful behavior people will want. Nah, from my side this is not necessary. Ciao, Dscho
next prev parent reply other threads:[~2019-07-12 10:29 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 [this message] 2019-07-31 5:58 ` Jeff King 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=nycvar.QRO.firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --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).