[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fw: git access

From: Trevor Daniels
Subject: Fw: git access
Date: Tue, 14 Jul 2009 08:35:10 +0100

copied to -devel for comment ....


----- Original Message ----- From: "Trevor Daniels" <address@hidden> To: "Mark Polesky" <address@hidden>; "Graham Percival" <address@hidden>
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  Yes, I just checked;
push.default seems to have been added around 1.6.

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.

This is exciting (and a little scary)!

When you're ready to push for real, try making
a small change to the text of a doc file first.
Anything you do can always be reverted, so no
need to worry.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]