commit - Strange behavior with git fetch -

-

i'm getting big problem git fetch...look this

$ git fetch server:project    422b4cb..a04c062  master     -> origin/master  $ git show-ref ba113be885e66a5306d1646cd3db0801170c04f8 refs/heads/alpha-release a04c062261beeb4a951337ebb58745945cac3562 refs/heads/master a04c062261beeb4a951337ebb58745945cac3562 refs/heads/test a04c062261beeb4a951337ebb58745945cac3562 refs/remotes/origin/head ba113be885e66a5306d1646cd3db0801170c04f8 refs/remotes/origin/alpha-release a04c062261beeb4a951337ebb58745945cac3562 refs/remotes/origin/master

and git fetch:

$ git fetch server:project  + a04c062...422b4cb head       -> origin/head  (forced update)  $ git show-ref ba113be885e66a5306d1646cd3db0801170c04f8 refs/heads/alpha-release a04c062261beeb4a951337ebb58745945cac3562 refs/heads/master a04c062261beeb4a951337ebb58745945cac3562 refs/heads/test 422b4cbac3db2784c8f6e94ffd99c7afcda9122d refs/remotes/origin/head ba113be885e66a5306d1646cd3db0801170c04f8 refs/remotes/origin/alpha-release 422b4cbac3db2784c8f6e94ffd99c7afcda9122d refs/remotes/origin/master

and one...

$ git fetch server:project    422b4cb..a04c062  master     -> origin/master  $ git show-ref ba113be885e66a5306d1646cd3db0801170c04f8 refs/heads/alpha-release a04c062261beeb4a951337ebb58745945cac3562 refs/heads/master a04c062261beeb4a951337ebb58745945cac3562 refs/heads/test a04c062261beeb4a951337ebb58745945cac3562 refs/remotes/origin/head ba113be885e66a5306d1646cd3db0801170c04f8 refs/remotes/origin/alpha-release a04c062261beeb4a951337ebb58745945cac3562 refs/remotes/origin/master

and git fetch:

$ git fetch server:project  + a04c062...422b4cb head       -> origin/head  (forced update)  $ git show-ref ba113be885e66a5306d1646cd3db0801170c04f8 refs/heads/alpha-release a04c062261beeb4a951337ebb58745945cac3562 refs/heads/master a04c062261beeb4a951337ebb58745945cac3562 refs/heads/test 422b4cbac3db2784c8f6e94ffd99c7afcda9122d refs/remotes/origin/head ba113be885e66a5306d1646cd3db0801170c04f8 refs/remotes/origin/alpha-release 422b4cbac3db2784c8f6e94ffd99c7afcda9122d refs/remotes/origin/master

my refs/remotes/origin/head , refs/remotes/origin/master force update 422b4cb...

what happened? 422b4cb... old commit.

wow...after big fight git fixed issue using:

git push origin :head


Comments

Post a Comment

Popular posts from this blog

c# - Is it possible to remove an existing registration from Autofac container builder? -

-
something along lines: builder.registertype<mytype>().as<itype>(); builder.registertype<mytype2>().as<itype>(); builder.deregistertype<mytype>().as<itype>() var container = builder.build(); var types = container.resolve<ienumerable<itype>>(); assert.istrue(types.count == 1); assert.istrue(types[0].gettype == typeof(mytype2)); scenario: go through bunch of assemblies , go register types want make sure have 1 implementation of given type. need before create container. track on own nice if autofac me bit. this cannot done directly using containerbuilder , unless start on new one. mind you, having first built container should able construct new container filtering away unwanted types , reusing registrations first container. this: ... var container = builder.build(); builder = new containerbuilder(); var components = container.componentregistry.registrations .where(cr => cr.activator.limittype != typ...
Read more

php - Mysql PK and FK char(36) vs int(10) -

-
i have read mysql can handle indexes , searches better if tables keys integers rather char(36) uuid's. is worth converting int(10)? note: use 1 server , have have plans use multiple databases concurrently therefore removing 1 of big reasons using uuid. our tables innodb if makes difference. thanks in advance. usually rdbms can handle integer keys pk more efficient, other datatypes. reason how build index column, yes: long dont require string (or other typed) keys, should use integers. however: char(36) , int(10) far away being equal, because int(10) much smaller, char(36). dont know, if require many different keys, should keep in mind. update, complete last paragraph: int(10) 32-bit, char(36) 36 - ^byte^ (= 288-bit). not mean, int consumes less space, means, char(36) has 4 times more different keys.
Read more