Michael Orlitzky <mjo <at> gentoo.org> writes:
> > No, those are all the correct names that git uses. Possibly years of > > using cvs/svn has trained your brain to think in a particular way. > > Git does not work that way. It's as different from svn as you can get > > for 2 reasons... I think you missed the point; There is a void between the install handbook and the Dev and Ebuild documents. That is how to use git(&github) as a user progresses along the pathway to near dev capabilities. Sure you can 'grind it out' on your own and if that is what folks want, then there should be 'no bitching' about not enough devs. If the Gentoo community decides 'hey it'd sure be nice to have many more devs' then the pathways is dimly lit, imho. > It all makes enough sense after you get used to it, but the problem is > that if you have some operation in mind and you read "git --help", then > you're going to guess the wrong command based on their names. Mercurial > and Darcs (which have a similar model) managed to get the names right. Yes, I get the differences. They are not 'show stoppers' for me, but I do believe the process of obtaining dev_level capabilities within the gentoo framework, would be much more pleasurable if some git documentation, customer tailored to gentoo was slowly develop over time on the gentoo wiki. > The git people call their low-level commands "plumbing," and the > user-interface "porcelain." New user have trouble because the porcelain > commands are named after what the plumbing does. It's like if the > find/replace tool in your word processor was called "depth-first regular > expression group match substitution", and not "find." OK, Git is not really that bit of a problem. It's finding the right hammer and tools to get it working seemlessly with what is going on within the dev efforts. Granted, much is still being worked out, I get that (and read about it). But user level maniputions of overlays and ebuild sources using git, is a bit of a 'walk once' atm, imho. Maybe in time somebody will just grab a git manual/doc and hammer on it so is looks and smells like a gentoo doc, and put it up in the wiki.... Maybe just a gentoo-user-howto for common user level tasks. Just expressing my opine, timely with Peter and other's comments and my own beliefs. Thanks for the comments, James
