Re: Difficulties in advertising a new branch to git newbies

From: Santi Béjar <sbejar@gmail.com>
Date: Jan 31, 2007, 19:27 UTC
Message-ID: <8aa486160701311127v686929c8vb9b5771031776ed8@mail.gmail.com>
In-Reply-To: <87odognuhl.wl%cworth@cworth.org>

On 1/30/07, Carl Worth <cworth@cworth.org> wrote:

> So here's a scenario I'm in right now. A user of my software reported a
> bug. I put together some patches to fix the bug and pushed them out as
> a new branch "proposed-fix" that I'd like the user to test.

Actually it is the same "problem" as when you want to work on the non-HEAD remote branch.

Currently I do (with current git):

git clone git://... git checkout -b ${branch} origin/${branch} git config branch.${branch}.merge refs/heads/${branch}

then they could update this with just:

git pull

It would be nice if:

git clone -b ${branch} git://...

would be equivalent of the above three commands.

Santi