push.default git config?

Felipe Sateler fsateler at gmail.com
Tue Aug 4 06:14:17 UTC 2009

(I'm finally back home, so I should be able to resume work normally.)

What are you using for the git configuration git.push? I'm getting this message 
from git push now:

% git push
warning: You did not specify any refspecs to push, and the current remote
warning: has not configured any push refspecs. The default action in this
warning: case is to push all matching refspecs, that is, all branches
warning: that exist both locally and remotely will be updated.  This may
warning: not necessarily be what you want to happen.
warning: You can specify what action you want to take in this case, and
warning: avoid seeing this message again, by configuring 'push.default' to:
warning:   'nothing'  : Do not push anything
warning:   'matching' : Push all matching branches (default)
warning:   'tracking' : Push the current branch to whatever it is tracking
warning:   'current'  : Push the current branch
<snip normal output>

While I think the default up to now has always been matching, I'm not sure it 
is the best option either. I think tracking is the correct option, but I fear 
I will fail to push the upstream branch because of the needed explicit step 
git push upstream origin.

Or maybe is it that I'm too lazy by assuming a svn-like workflow and using git 
push without arguments?

Felipe Sateler
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20090804/a1f4ebab/attachment.pgp>

More information about the pkg-multimedia-maintainers mailing list