From: Alan Chandler Date: Sun, 18 Sep 2005 12:47:11 GMT Subject: Re: Newbie falls at first hurdle Message-ID: <200509181347.11403.alan@chandlerfamily.org.uk> In-Reply-To: <46a038f9050918035436352f71@mail.gmail.com> On Sunday 18 Sep 2005 11:54, Martin Langhoff wrote: > On 9/18/05, Horst von Brand wrote: > > The easiest way of doing this is using cogito (near where you found > > git). It automates some tasks using git as backendq, in this case it > > would only need: > > > > cg-init > > +1 -- I work with a small team and we are migrating to cogito/git. > There's still a few things we have to call git utilities for (change > branch, for instance) but for "intuitive" usage, cogito is the cat's > whiskers. Yes - I had increasingly believed that with all the scripts being generated with git that cogito was becoming irrelevant. However experience of the last day has shown me that is far from the case. I really like cg-commit where it lists the files its going to commit for you, and where if you delete the line it doesn't. If I've been doing a bit too many things at once it helps commit in small chunks Seems cogito branch handling only really deals with linking to others. I have ended up also using git branch and git checkout -f to keep lots of little local branches in my repository. Still struggling with how to cherry pick parts a previous update (between possibly two other branches) and apply them to a current branch - all the tutorials assume you want it all, and I can't really understand what the cherry pick commands do from their manuals. -- Alan Chandler http://www.chandlerfamily.org.uk