From: Miles Bader <miles@gnu.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Rudolf Polzer <divVerent@alientrap.org>,
Tay Ray Chuan <rctay89@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] git push --track
Date: Fri, 15 Jan 2010 09:30:20 +0900 [thread overview]
Message-ID: <87y6k06wgz.fsf@catnip.gol.com> (raw)
In-Reply-To: <7vr5ps5jx1.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Thu, 14 Jan 2010 15:46:50 -0800")
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.
next prev parent reply other threads:[~2010-01-15 0:30 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 15:12 [PATCH] git push --track Rudolf Polzer
2010-01-13 15:43 ` Ilari Liusvaara
2010-01-13 15:55 ` Rudolf Polzer
2010-01-13 16:27 ` Ilari Liusvaara
2010-01-13 16:37 ` Matthieu Moy
2010-01-14 5:21 ` Tay Ray Chuan
2010-01-14 7:00 ` Rudolf Polzer
2010-01-14 23:13 ` Junio C Hamano
2010-01-14 7:16 ` Jeff King
2010-01-15 5:47 ` Junio C Hamano
2010-01-15 14:00 ` Rudolf Polzer
2010-01-15 15:45 ` Miles Bader
2010-01-15 18:16 ` Junio C Hamano
2010-01-14 0:28 ` Miles Bader
2010-01-14 0:25 ` Miles Bader
2010-01-14 0:33 ` Johannes Schindelin
2010-01-14 0:36 ` Miles Bader
2010-01-14 0:46 ` Miles Bader
2010-01-14 7:01 ` Rudolf Polzer
2010-01-14 13:44 ` Martin Langhoff
2010-01-14 14:16 ` Johannes Schindelin
2010-01-14 14:25 ` Matthieu Moy
2010-01-14 14:35 ` Martin Langhoff
2010-01-14 15:27 ` Andreas Krey
2010-01-14 1:27 ` Tay Ray Chuan
2010-01-14 1:35 ` Miles Bader
2010-01-14 1:37 ` Tay Ray Chuan
2010-01-14 1:49 ` Miles Bader
2010-01-14 1:58 ` Tay Ray Chuan
2010-01-14 7:03 ` Rudolf Polzer
2010-01-14 23:46 ` Junio C Hamano
2010-01-15 0:30 ` Miles Bader [this message]
2010-01-15 18:18 ` Junio C Hamano
2010-01-15 18:54 ` Miles Bader
2010-01-15 13:26 ` Matthieu Moy
2010-01-14 6:41 ` Nanako Shiraishi
2010-01-14 7:08 ` Rudolf Polzer
2010-01-14 10:31 ` Johannes Schindelin
2010-01-14 22:27 ` Nanako Shiraishi
2010-01-14 23:50 ` Junio C Hamano
2010-01-15 13:44 ` Rudolf Polzer
2010-01-15 14:09 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y6k06wgz.fsf@catnip.gol.com \
--to=miles@gnu.org \
--cc=divVerent@alientrap.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rctay89@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).