From: John Tapsell Date: Fri, 13 Mar 2009 10:07:15 GMT Subject: Re: [RFC/PATCH] git push usability improvements and default change Message-ID: <43d8ce650903130307u2944ca8n3191ca7c9fb7e30f@mail.gmail.com> In-Reply-To: Hi, What's the status of these patches? Will be commited? John 2009/3/13 Miles Bader : > Finn Arne Gangstad writes: >>> 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 >> >> Yes, git push --track ... would typically do the same thing to the >> config as git checkout -b MY-BRANCH SOME_REMOTE/REMOTE-BRANCH, which >> is enough for push --tracking to do its thing. >> >> I am not sure if you mean that git push --track could do something >> extra to make --tracking unecessary for git push, currently it cannot >> do that since the push configuration is per remote, not per branch. > > Hmm, now I'm confused... I was just thinking about --track, but am not > sure what --tracking is ... need to go grovel past posts... > > -Miles > > -- > Happiness, n. An agreeable sensation arising from contemplating the misery of > another. > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at  http://vger.kernel.org/majordomo-info.html >