From: Liu Yubao <yubao.liu@gmail.com>
To: Miles Bader <miles@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: Do most people feel tracking branches useful?
Date: Wed, 29 Oct 2008 17:58:05 +0800 [thread overview]
Message-ID: <490833AD.70806@gmail.com> (raw)
In-Reply-To: <buoprlj4vle.fsf@dhapc248.dev.necel.com>
Miles Bader wrote:
> Liu Yubao <yubao.liu@gmail.com> writes:
>> do most people feel tracking branches useful?
>
> Extremely useful. I usually keep local branches closely synchronized
> with a remote "central" version, and tracking branches make the frequent
> push/pull much more convenient.
>
In my work flow, I don't keep changes in local branch for long time,
I rebase it regularly and push them to central branch or discard them
if the upstream rejects.
You are right, I realize tracking branches is useful for people who keeps
local changes for long time and track the upstream branch at the same time.
But I guess an auto-rebasing policy is more sensible than auto-merging policy
because I won't get many useless "Merge branch 'xxx' of ..." messages in the
history.
Another problem about tracking branch is `git pull` won't merge tracking branch
with remote branch when the current branch isn't tracking branch, it warns me
"You asked me to pull without telling me which branch you ....". It's not
convenient to checkout tracking branch and execute `git pull` then switch back
to my working branch.
next prev parent reply other threads:[~2008-10-29 9:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 8:55 Do most people feel tracking branches useful? Liu Yubao
2008-10-29 9:08 ` Miles Bader
2008-10-29 9:58 ` Liu Yubao [this message]
2008-10-29 13:29 ` Miles Bader
2008-10-29 9:48 ` Andreas Ericsson
2008-10-29 10:22 ` Liu Yubao
2008-10-29 11:53 ` Andreas Ericsson
2008-10-29 10:03 ` Björn Steinbrink
2008-10-29 10:38 ` Liu Yubao
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=490833AD.70806@gmail.com \
--to=yubao.liu@gmail.com \
--cc=git@vger.kernel.org \
--cc=miles@gnu.org \
/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).