Re: [PATCH] git push --track
- From
Miles Bader <miles@gnu.org>
- Date
- Jan 14, 2010, 01:49 UTC
- Message-ID
- <fc339e4a1001131749s4da9526bs13406571773c38fd@mail.gmail.com>
- In-Reply-To
- <be6fef0d1001131737i59b2e843ib032c30027520b54@mail.gmail.com>
On Thu, Jan 14, 2010 at 10:37 AM, Tay Ray Chuan <rctay89@gmail.com> wrote:
Show 9 quoted lines
>> I very often create local branches and only later decide that I'd also >> like to push them to a remote -- but just as often, or more often, I >> never do so. It would be extremely annoying if I had to make that >> decision at branch-time. > > I'm not saying that the feature should belong to git-branch and so you > have to make this decision at branch time - I'm saying that since this > has got to do with modifying branches (sort of), it should be in > there.
I, and it appears other people, want to make this association at push-time -- that's almost always when I make the decision "I'd like to track this" -- so the most convenient and intuitive thing would be to have a --track option to push.
Of course there could _also_ be some sort of branch sub-command (or another command) to setup or change tracking state without pushing. But "push --track" is more important for normal usage I think.
-miles
-- Do not taunt Happy Fun Ball.