From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>, git@vger.kernel.org
Subject: Re: [PATCH] Add push --set-upstream
Date: Fri, 15 Jan 2010 13:01:46 -0800 [thread overview]
Message-ID: <7vvdf3ulol.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <vpqy6jzuwpv.fsf@bauges.imag.fr> (Matthieu Moy's message of "Fri\, 15 Jan 2010 18\:03\:24 +0100")
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> Ilari Liusvaara <ilari.liusvaara@elisanet.fi> writes:
>
>> +
>> +-u::
>> +--set-upstream::
>> + For every branch that is up to date or successfully pushed, add
>> + upstream (tracking) reference for argument-less git pull.
>
> Not just argument-less git pull. git status is also impacted for
> example. Actually, we already have documentation for it in git-branch
> (--track option), and git-config (branch.<name>.merge configuration
> variable), so you should add a pointer to one of them.
>
> How about
>
> --set-upstream::
> For every branch that is up to date or successfully pushed, add
> upstream (tracking) reference, used by argument-less
> linkgit:git-pull[1] and other commands. For more information,
> see 'branch.<name>.merge' in linkgit:git-config[1].
Yeah, if we talked only about the configuration variable it wouldn't help
users, but this description is reayy good.
> Or the --track option of branch and checkout should be renamed as
> --set-upstream, but that seems a lot of trouble for little benefit.
It might make sense to do so in the longer term UI clean-up, but I think
that is largely an independent topic. By not introducing new places the
confusing --track is used, we are at least not making things worse.
next prev parent reply other threads:[~2010-01-15 21:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 16:36 [PATCH] Add push --set-upstream Ilari Liusvaara
2010-01-15 17:03 ` Matthieu Moy
2010-01-15 17:12 ` Johannes Schindelin
2010-01-15 21:01 ` Junio C Hamano [this message]
2010-01-15 17:17 ` Jeff King
2010-01-15 17:42 ` Jeff King
2010-01-15 22:06 ` Ilari Liusvaara
2010-01-15 22:08 ` Jeff King
2010-01-15 18:19 ` Junio C Hamano
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=7vvdf3ulol.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=ilari.liusvaara@elisanet.fi \
/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).