From: Liu Yubao <yubao.liu@gmail.com>
To: git@vger.kernel.org
Subject: Do most people feel tracking branches useful?
Date: Wed, 29 Oct 2008 16:55:48 +0800 [thread overview]
Message-ID: <49082514.9050405@gmail.com> (raw)
Hi,
I often feel tracking branches are useless to me, because there are remote
branches and I work on my private branch in most time.
repos
|
|-- my (private branch, do my dirty work)
|-- master (tracking branch)
|-- origin/master (remote branch)
To avoid conflict when execute `git pull` and make the history linear, I work
on branch "my" instead of "master". Here is my work flow:
1) use `git fetch` or `git remote update` to synchronize branch "origin/master"
with branch "master" in remote repository;
2) create a new private branch to polish my commits and rebase it against
"origin/master";
3) at last push this new branch to the remote repository or ask the upstream
developer to fetch it(no `git pull` because we want history as linear as possible).
I don't want to bother with the tracking branch "master", it's identical
with "origin/master". Because `git checkout -b xxx <remote_branch>`
will create a tracking branch "xxx" by default, so my question is:
do most people feel tracking branches useful?
BTW: I feel the terminalogy "remote branch" is confused, because I must
synchronize it with `git fetch`. I feel it's better to call it "tracking
branch" // seems will lead to bigger confusion to experienced git users:-(
next reply other threads:[~2008-10-29 8:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 8:55 Liu Yubao [this message]
2008-10-29 9:08 ` Do most people feel tracking branches useful? Miles Bader
2008-10-29 9:58 ` Liu Yubao
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=49082514.9050405@gmail.com \
--to=yubao.liu@gmail.com \
--cc=git@vger.kernel.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).