fedpkg: Change in git push method?

[Michael J Gruber]

Josh Boyer venit, vidit, dixit 08.02.2013 18:56:
> On Fri, Feb 8, 2013 at 12:54 PM, Thomas Moschny
> <thomas.moschny at gmail.com> wrote:
>> 2013/2/8 Josh Boyer <jwboyer at gmail.com>:
>>> Yes, but fedpkg is currently relying on the existing git default, which
>>> is matching.  That is changing upstream in git, so fedpkg needs to set
>>> a default when it clones.
>>
>> And this default should probably be push.default=upstream.
> 
> Sure, that's certainly possible.
> 
> josh

That git message is pretty clear about "matching" being the former
default,so that is what fedpkg relies upon.

Note that "upstream" (i.e. the forthcoming git default) might be a
better default for fedpkg, but that would be a change in behavior for
fedpkg. ("upstream" is synonymous to "tracking")

The problem is that "fedpkg push" starts to fail on existing clones, and
changing "fedpkg clone" doesn't help with that.

Could it be that "fedpkg clone" used to set the default to "tracking"?

In any case, "fedpkg push" should use a specific refspec, or else its
behaviour will depend on the user config.

Michael