On Fri, 04 Oct 2013 11:42:35 +0200 Bertrand Jacquin <be...@meleeweb.net> said:
> > steps 3, 4, 5, 6, 8... are an incantation. to be done in that order. > > there is > > --no-ff... and he series.. its a DEFINITE incantation. read up on git > > as a > > leaky abstraction. it is very much one. it forces peole to learn a > > series of > > incantations/steps all the time as opposed to just having a single "do > > X" where > > X is always the same series of steps. why do it by hand. why have to > > LEARN by > > heart and then of course get it wrong at times.... > > Officially, raster is now a high level manager ! > > Theses incantation are quite straight forward when you use git daily. > Not at the first use, but become fast essential. i use git every day.. but i dont go making private branches and merging them. even then, take a look at my aliases and scripts dir. i fail to understand how many people survive doing everything manually by hand. i see it all around me. they do the full command like: ps -ef | grep X when i do: psg X why? i get tired of memorizing N steps or magic incantations. i do NOT do: ./autogen.sh && make && sudo make install i do: cmi i never do: make && sudo make install i do: mi why? i can't stand having to memorize a tonneof obscure incantations that make little sense outside of the leaky abstraction that is git: http://steveko.wordpress.com/2012/02/24/10-things-i-hate-about-git/ https://news.ycombinator.com/item?id=3891598 you may love doing it all by hand and find great pleasure in twisting your brain to work and think like gits internals do, but i do not. i want to perform a simple task and git turns it into a job of remembering a magic incantation. i keep now having to build scripts that wrap git stuff up so i dont have to do N steps and maybe forget one. the same people who say "omg git is so awesome! it has git bisect! svn sucks! it is the worst thing. it doesnt have bisect" have a set of standards that think doing other SIMPLE stuff that svn does in a single cmd is ok to break into a dozen steps in git with a bunch of cmdline opts u have to keep looking up, and if in svn i had to write a small script to do a bisect (which was perfectly possible too) then svn insta-sucks. but having to wrap up git or memorize a vast series of steps for everything u need to do in git is perfectly fine and great! git is a poor tool. it's interface is poor. it does some cool stuff - but as a tool it is poor. if you want people to follow conventions/procedures, don't make them have to read your powerpoint on them and study them and memorize the document/process. (and the people here know what i'm referring to). make the TOOL doe the thing for you obviously and simply. for git that would normally mean patching it (not as easy), but a simple wrapper does the job. don't define a document to describe a process - encapsulate it in a simple tool (script). -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
