From: Miles Bader <miles@gnu.org>
Date: Thu, 12 Mar 2009 10:52:29 GMT
Subject: Re: [RFC/PATCH] git push usability improvements and default change
Message-ID: <buomybrqahe.fsf@dhlpc061.dev.necel.com>
In-Reply-To: <20090312102243.GA27665@pvv.org>

Finn Arne Gangstad <finnag@pvv.org> writes:
> The main problem with all these examples is that the underlying
> assumption is that you can always use the same branch name locally and
> remotely.

Presumably the push --track option would be used with an explicit branch
name given to push anyway, right?  Then it can use that info to set up
the tracking flexibly (and with sane defaults).

E.g.,, simple case:

    git push --track SOME_REMOTE BRANCH_NAME

complex case:

    git push --track SOME_REMOTE MY-BRANCH:REMOTE-BRANCH

-Miles

-- 
=====
(^o^;
(()))
*This is the cute octopus virus, please copy it into your sig so it can spread.