Re: [PATCH] git push --track
- From
Miles Bader <miles@gnu.org>
- Date
- Jan 15, 2010, 00:30 UTC
- Message-ID
- <87y6k06wgz.fsf@catnip.gol.com>
- In-Reply-To
- <7vr5ps5jx1.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> Yes, "push --track" lets you postpone the decision; branching, working on > it, pushing it out _and_ _then_ using your "branch -f" trick will let you > postpone the decision even further.
Nonetheless, "push --track" is by far the most natural UI for the most common case, I think.
> And it doesn't add --track to the UI.
That's not a positive...
None of this is _necessary_, it's to make git more convenient.
Halfway-measures seem like "oh the user can just use this branch command" seem like, well, halfway measures. Sure, it would be nice to have a branch command _too_, just to make it easier for branch maintenance, but it's not what's really wanted.
-Miles
-- Faith, n. Belief without evidence in what is told by one who speaks without knowledge, of things without parallel.