Re: Back quote typo in error messages (?)

2017-02-16 Thread Fabrizio Cucci
On 16 February 2017 at 19:02, Jeff King wrote: > Try the "Quoted Text" section of the original asciidoc user manual: > > http://www.methods.co.nz/asciidoc/userguide.html#X51 > > Asciidoctor has introduced some new syntax (almost certainly because the > original asymmetric formulations have a bun

Re: Back quote typo in error messages (?)

2017-02-16 Thread Fabrizio Cucci
On 15 February 2017 at 21:56, Jeff King wrote: > Grep for "``" in Git's documentation directory, and you will see many > examples (asciidoc only accepts the double-quote form, not singles). > > You can also try: > > echo "this is \`\`quoted'' text" >foo.txt > asciidoc foo.txt > > and then open

Re: Back quote typo in error messages (?)

2017-02-15 Thread Fabrizio Cucci
On 15 February 2017 at 21:21, Jeff King wrote: > On Wed, Feb 15, 2017 at 09:06:46PM +0000, Fabrizio Cucci wrote: >> Shouldn't the wrong flag be surrounded by two single quotes instead of >> a back quote and a single quote? > > Some people use the matched backtick/s

Back quote typo in error messages (?)

2017-02-15 Thread Fabrizio Cucci
Hello everyone, it's been a couple of days that I keep noticing something (very minor) that my OCD for symmetric things can't really stand. If you run the following command: $ git branch --i-dont-exists you should get: error: unknown option `i-dont-exists' Shouldn't the wrong flag be surround

error: Can't cherry-pick into empty head

2016-05-28 Thread Fabrizio Cucci
Hello everyone, I'm trying to understand why I'm getting the error as per subject. The scenario is the following: I'm on the master branch (which contains several commits) and I would like to create a new empty branch (let's call it new-orphan) and cherry-pick only the commits related to a specif