Re: Invalid refspec?

Daniel Barkalow [off-list ref] writes:

... but there's no particular need to give a 
different error for "HEAD~1:foo" versus 
"e83c5163316f89bfbde7d9ab23ca2e25604af290:foo" based on the presence of a 
~.

This is a valid argument in that e83c51... could be (and currently has to
be) a ref name in a fetch refspec.

But we still need to reject something like "HEAD**1:foo".