Hello Jim, any chance you could check whether the Libtool git tree on savannah is non-bare? If yes, then we may want to fix that (but I'd have to check how to do that). See Peter's report below.
Thanks, Ralf * Peter Rosin wrote on Fri, Sep 11, 2009 at 08:42:46AM CEST: > Den 2009-09-10 19:55 skrev Ralf Wildenhues: > >* Peter Rosin wrote on Thu, Sep 10, 2009 at 10:06:32AM CEST: > >> 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
