On 03/05/13 11:38, Carsten Haitzler (The Rasterman) wrote: > On Fri, 03 May 2013 10:52:38 +0100 Daniel Willmann <d.willm...@samsung.com> > said: > >> On 03/05/13 00:12, Carsten Haitzler (The Rasterman) wrote: >>> On Thu, 2 May 2013 15:12:00 +0100 Tom Hacohen <t...@stosb.com> said: >>> >>>> git push >>>> pushes tracking branches to their respective remote branchs on all >>> remotes. >>>> If you want to push the current branch on top of master you should do: >>>> git push origin current_branch:master >>>> Assuming origin is the wanted remote. >>> >>> i wasnt expecting to have another invisible branch. i was expecting to >>> push what >>> i see now (the code i have not that i did a git commit on). i did have a >>> conflict while trying to revert 2 commits and gave up by doing a git reset >>> --hard but that left me in (no branch)... and i didnt realize. >> >> pushing what you have now is done with >> git push origin HEAD:master assuming you want to push to master branch >> on origin. >> >> Without options git will push the tracking branches as Tom already said. >> HEAD is always referencing the latest commit you checked out/made/... on >> your current branch. > > as said already. poor interface. git requires you have to remember a whole new > set of magic incantations for it to do what is intuitive/obvious/you are used > to. >
I could not agree more !! ;) dh ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel