On Thursday, February 15, 2007 at 16:58:16 (-0500) Jeff King writes: >On Thu, Feb 15, 2007 at 03:53:01PM -0600, Bill Lear wrote: > >> Is this really the way 1.4.4.1 works? I have (mistakenly) been >> working on my tracking branch, committing to it, pushing it, pulling >> in from elsewhere, shifting to new branches, etc., and I haven't lost >> anything, and can't see what harm I've done... > >Sorry, I thought you were talking about v1.5. v1.4.* does not have the >detached HEAD feature, and the default layout is to keep tracking and >local branches in the same namespace. This means that you can checkout >and commit to a tracking branch just as a local branch, and all changes >will be saved. It will only bite you later, when you try to fetch into >that tracking branch and realize that the fetch is not a fast-forward >(remember the troubles you were having with fetches and pushes last >week? Those were caused by working on the tracking branches). Ok, just wanted confirmation of my (in)sanity. >> > git checkout -b topic origin/topic >> >> Sure, it is easy, but it's surprising to (our) users when they >> do a clone and can't "jump right in", and have to spend 3 seconds >> doing the above... > >Fair enough. It should be pretty simple to implement; why don't you try >working up a patch? :) Well, I seriously thought about it, but the git-clone code is pretty dense. It might be educational though, and since I'm the only one who wants it ... might be worth a shot. Thank you for your help. Bill - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html