Re: [PATCH] Documentation: update git-pull.txt for clone's new default behavior
- From
- J. Bruce Fields <bfields@fieldses.org>
- Date
- Jan 2, 2007, 00:10 UTC
- Message-ID
- <20070102001044.GB32148@fieldses.org>
- In-Reply-To
- <182318.86313.qm@web31812.mail.mud.yahoo.com>
On Mon, Jan 01, 2007 at 04:01:15PM -0800, Luben Tuikov wrote:
Show 7 quoted lines
> --- "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).
--b.