In <[EMAIL PROTECTED]>, Gerrit Pape wrote: > On Sun, Sep 02, 2007 at 11:39:33PM +0100, Tony Houghton wrote: > > When I call git-push ssh://... from a remote machine (specifically in > > this case my laptop with Ubuntu Gutsy) the files I've altered don't get > > updated in the target repository. The changes show up in gitk and if I > > clone the repository the files are changed in the new copy. I think if > > you perform an operation in the original target repository that would > > change the files eg switching to a different branch and back again, the > > updates do get applied then, but I'm not sure. > > Hi Tony, if I understand you correctly, this is expected behaviour. If > you push into a non-bare (with working tree) repository, the working > tree isn't updated automatically. The working tree might have local > changes, that either get overridden, or might require a merge with > possible conflicts. After you pushed into a non-bare repository, you > can 'refresh' the working tree there by doing 'git checkout -f'; note > that this overrides local changes. Read about hooks in git if you want > to have this done automatically.
Thanks for the explanation. That doesn't seem to be made clear anywhere in the docs and it was unexpected because AFAIK the working tree was in sync with the repository before the push. -- TH * http://www.realh.co.uk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
