Re: [ITCH] Specify refspec without remote

Jeff King wrote:

To flesh out my earlier example:

  $ git clone https://github.com/upstream/project.git
  $ cd project
  $ hack hack hack; commit commit commit
  $ git tag -m 'something of note' my-tag
  $ git remote add me https://github.com/me/project.git
  $ git config branch.master.remote me
  $ git tag -m 'something of note'
  $ git push master my-tag

My intent there is publish both master and mytag, but my-tag goes to
origin. It's obvious if you think carefully about (and know) the rules,
and it's user error. But what fault do we take for designing a feature
that causes confusion?

Good example.  Sorry, I misunderstood your one-liner.  I agree that
this is confusing.  Tags are a bit of an outlier, and we have to think
of some way to behave sensibly with them.  I'll let you know if I
think of something in the next few hours.