Re: Cannot push anything via export transport helper after push fails.

В Sat, 11 May 2013 08:57:14 -0500 Felipe Contreras пишет: > On Sat, May 11, 2013 at 7:29 AM, Andrey Borzenkov wrote: > > I noticed that using git-remote-bzr, but as far as I can tell this is > > generic for all transport helpers using fast-export. > > > > > >

Re: Cannot push anything via export transport helper after push fails.

В Sat, 11 May 2013 08:57:14 -0500 Felipe Contreras пишет: > > > > The problem seems to be that git fast-export updates marks > > unconditionally, whether export actually applied or not. So next time > > it assumes everything is already exported and does nothing. > > > > Is it expected behavior? >

Re: Cannot push anything via export transport helper after push fails.

В Sat, 11 May 2013 13:36:26 +0100 John Keeping пишет: > On Sat, May 11, 2013 at 04:29:36PM +0400, Andrey Borzenkov wrote: > > I noticed that using git-remote-bzr, but as far as I can tell this is > > generic for all transport helpers using fast-export. > > > > >

Cannot push anything via export transport helper after push fails.

I noticed that using git-remote-bzr, but as far as I can tell this is generic for all transport helpers using fast-export. What happened was "git push" failed due to merge conflict. So far so good - but from now on git assumes everything is up to date. bor@opensuse:/tmp/test/git> git push origi

branch name in remote..push is not updated after "git branch -m"

I renamed branches and noticed that branch name was not changed in remote push config. I.e. after bor@opensuse:~/src/bootinfoscript> git branch -m github master I still have [remote "github"] push = github:master url = git://github.com/arvidjaar/bootinfoscript.git pushurl