libtool-patches
[Top][All Lists]
Advanced

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

Re: [SCM] GNU Libtool branch, pr-msvc-support, updated. v2.2.6-182-gdd42


From: Peter Rosin
Subject: Re: [SCM] GNU Libtool branch, pr-msvc-support, updated. v2.2.6-182-gdd42e63
Date: Fri, 11 Sep 2009 08:42:46 +0200
User-agent: Thunderbird 2.0.0.23 (Windows/20090812)

Den 2009-09-10 19:55 skrev Ralf Wildenhues:
Hi Peter,

* Peter Rosin wrote on Thu, Sep 10, 2009 at 10:06:32AM CEST:
The branch, pr-msvc-support has been updated
       via  dd42e63ce688302500f349606c55bf173feda3a4 (commit)
[...]
commit dd42e63ce688302500f349606c55bf173feda3a4
Merge: a128e6d5f8a57c0f3cfb85a28d8d843f504a3cdf 
b03736353b6d478a68bfc19c017605eb21a3edce
Author: Peter Rosin <address@hidden>
Date:   Wed Sep 9 12:36:23 2009 +0200

    Merge branch 'master' into pr-msvc-support

Thank you!
Ralf

No problem, it was overdue anyway...

But, I got this message when I made the push:

warning: updating the current branch
warning: Updating the currently checked out branch may cause confusion,
warning: as the index and work tree do not reflect changes that are in HEAD.
warning: As a result, you may see the changes you just pushed into it
warning: reverted when you run 'git diff' over there, and you may want
warning: to run 'git reset --hard' before starting to work to recover.
warning:
warning: You can set 'receive.denyCurrentBranch' configuration variable to
warning: 'refuse' in the remote repository to forbid pushing into its
warning: current branch.
warning: To allow pushing into the current branch, you can set it to 'ignore';
warning: but this is not recommended unless you arranged to update its work
warning: tree to match what you pushed in some other way.
warning:
warning: To squelch this message, you can set it to 'warn'.
warning:
warning: Note that the default will change in a future version of git
warning: to refuse updating the current branch unless you have the
warning: configuration variable set to either 'ignore' or 'warn'.

So, it appears that the repo at savannah isn't "bare" and that
pr-msvc-support is the currently checked out branch there? Or
am I barking up the wrong tree?

Cheers,
Peter




reply via email to

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