On Tue, Jul 14, 2009 at 08:35:10AM +0100, Trevor Daniels wrote: > > ----- Original Message ----- From: "Trevor Daniels" > <t.dani...@treda.co.uk> > To: "Mark Polesky" <markpole...@yahoo.com>; "Graham Percival" > <gra...@percival-music.ca> > Sent: Tuesday, July 14, 2009 8:33 AM > Subject: Re: git access >> >> Mark, you wrote Tuesday, July 14, 2009 5:50 AM >>> >>> Trevor Daniels wrote: >>>> Next try a push with --dry-run. Enter: >>>> git push --dry-run -v ssh+git://sv/srv/git/lilypond.git/ >>> >>> $ gt push --dry-run -v ssh+git://sv/srv/git/lilypond.git/ >>> 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: >>> 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 >>> Pushing to ssh+git://sv/srv/git/lilypond.git/ >>> To ssh+git://sv/srv/git/lilypond.git/ >>> = [up to date] master -> master >>> Everything up-to-date >>> >>> So far so good? >> >> Yes, I think so. I've never seen this sequence >> of warning messages, even though I do not have >> an entry for push.default in git config. You >> will have a more recent version of git than I >> do, so maybe this warning is a recent addition. >> I'm on 1.5.4.2.1161.g1a6f0. Yes, I just checked; >> push.default seems to have been added around 1.6.
Yes, no need to worry. This giant warning was added in 1.6.3. When I first tried to push with no arguments, I got this warning too. >>> Do you recommend setting 'push.default' to 'nothing'? >> >> No; you don't really want to have to specify source >> and destination on every push. In the simple git >> arrangement used by LilyPond the default "matching" >> is probably the best option. But as I'm not an >> expert, and don't have git 1.6, I'll copy to -devel >> for comment. I set 'push.default' to 'nothing' but it's really personal choice. Since pushing to master is (IMO) a relatively serious thing, I would rather type the more verbose version: $ git push origin master than accidentally type "git push" when I meant to type "git pull". This way, I can differentiate between pushing and pulling more easily, and it provides a safeguard in that $ git push will no longer work. HTH, Patrick _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
