Re: [PATCH] Documentation: update git-pull.txt for clone's new default behavior

From: Luben Tuikov <ltuikov@yahoo.com>
Date: Jan 2, 2007, 01:28 UTC
Message-ID: <65526.67561.qm@web31806.mail.mud.yahoo.com>
In-Reply-To: <20070102001044.GB32148@fieldses.org>

--- "J. Bruce Fields" <bfields@fieldses.org> wrote:

Show 23 quoted lines

> On Mon, Jan 01, 2007 at 04:01:15PM -0800, Luben Tuikov wrote:
> > --- "J. Bruce Fields" <bfields@fieldses.org> wrote:
> > > -The common `Pull: master:origin` mapping of a remote `master`
> > > -branch to a local `origin` branch, which is then merged to a
> > > -local development branch, again typically named `master`, is made
> > > -when you run `git clone` for you to follow this pattern.
> > 
> > So is this no longer the case?
> 
> Right; that mapping is no longer what git clone sets up for you.
> 
> > Can someone please bring me up to date?
> > 
> > What is going on?
> 
> The simplest way to understand the current behavior is probably to
> install the latest git, read the git-clone man page, clone a new
> repository, and take a look at it.
> 
> Remote branches are stored in separate namespaces under
> .git/refs/remotes/, so that they don't muck up your view of your local
> branches, and so git can enforce different policies for them (such as
> forbidding committing to them).

Smells like another "newbie" protection.

Let me understand, someone here installed git, didn't read the then man page of git-clone/pull/fetch, screwed up their repo, and decided to change established behavior.

Regardless, I think addressable (named) branch specs are the way to go. This will as well, unify/reconcile remotes/ and local stuff, since it is already implemented for remotes/ .

     Luben