From: Michael K. Edwards <medwards.linux@gmail.com>
Date: Fri, 17 Nov 2006 06:42:55 GMT
Subject: Re: Cleaning up git user-interface warts
Message-ID: <f2b55d220611162242s48dc42d6g4cbfd9173e712ff8@mail.gmail.com>
In-Reply-To: <f2b55d220611161734m49136e6fneda5b002eb67618b@mail.gmail.com>

On 11/16/06, Michael K. Edwards <medwards.linux@gmail.com> wrote
>   The only entry placed in .git/remotes is the
> "origin" of the new clone, which is the "master" of the remote
> repository.  That's for the user's convenience, and is about the only
> thing in the new clone that _isn't_ a copy of something in the remote
> tree.

Actually, this "origin" entry does contain "Pull:" lines for all of
the branches that were cloned, so that "git pull" fetches and merges
updates to all of these branches.  (If upstream is in the habit of
reverting things, you may need "git pull -f"; I just did that on the
git repo to handle a failure to fast-forward on the "pu" branch.)

Presumably "git branch -D" should inspect everything under
.git/remotes to see whether one or more Pull: lines need to be deleted
along with the branch.  Currently, it looks like "remotes" entries are
created only by "git clone" or by hand.  Junio, are there any plans to
manage the contents of "remotes" through the tool instead of by hand?

Cheers,