From: Junio C Hamano <gitster@pobox.com>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: "John M. Dlugosz" <ngnr63q02@sneakemail.com>, git@vger.kernel.org
Subject: Re: setting up tracking on push
Date: Wed, 11 Mar 2009 18:11:48 -0700 [thread overview]
Message-ID: <7vprgnlf3f.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <76718490903111758l4e4bd29et379e975deb8e99bd@mail.gmail.com> (Jay Soffian's message of "Wed, 11 Mar 2009 20:58:59 -0400")
Jay Soffian <jaysoffian@gmail.com> writes:
> On Wed, Mar 11, 2009 at 8:08 PM, John M. Dlugosz
> <ngnr63q02@sneakemail.com> wrote:
>> On a related note, what exactly does "tracking" mean? I know that I can
>> push/pull local names that match up with names on the origin, and that the
>> latter are in the remotes/origin subdirectory. Those are what I think are
>> called "remote tracking branches". Or is that just a part of the whole
>> story? What is the correct nomenclature?
>
> http://article.gmane.org/gmane.comp.version-control.git/54822/
I do not think the description of remote-tracking in that article is
correct. We use the word to call remote/origin/<name> that keeps copies
of what we saw over there when we last observed.
The way to mark local branches to merge with/rebase onto something else
by default is --track option to "git branch" and "git checkout -b", and
that is often used to mark them to --track remote-tracking branches but
they do not have to --track remote-tracking branches. They can --track
local branches as well.
next prev parent reply other threads:[~2009-03-12 1:13 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 3:07 setting up tracking on push Miles Bader
2009-03-06 3:17 ` John Tapsell
2009-03-06 4:49 ` Jay Soffian
2009-03-06 10:45 ` Johannes Schindelin
2009-03-06 11:15 ` Miles Bader
2009-03-06 14:15 ` Jeremy O'Brien
2009-03-06 15:43 ` Jay Soffian
2009-03-06 16:29 ` Miles Bader
2009-03-10 20:26 ` Marc Branchaud
2009-03-10 23:09 ` Jeff King
2009-03-11 1:52 ` Jay Soffian
2009-03-11 2:04 ` Jeff King
2009-03-11 2:59 ` Jay Soffian
2009-03-11 3:06 ` Jeff King
2009-03-11 3:40 ` Jay Soffian
2009-03-11 3:44 ` Jay Soffian
2009-03-11 3:57 ` Jeff King
2009-03-11 4:15 ` Jay Soffian
2009-03-24 9:58 ` Jakub Narebski
2009-03-11 4:37 ` Junio C Hamano
2009-03-11 4:56 ` Miles Bader
2009-03-11 5:03 ` Miles Bader
2009-03-11 5:22 ` Jay Soffian
2009-03-11 21:39 ` Marc Branchaud
2009-03-11 6:32 ` Jeff King
2009-03-11 10:02 ` Nanako Shiraishi
2009-03-11 16:40 ` Jeff King
2009-03-12 0:08 ` John M. Dlugosz
2009-03-12 0:58 ` Jay Soffian
2009-03-12 1:11 ` Junio C Hamano [this message]
2009-03-12 1:16 ` Jay Soffian
2009-03-12 1:14 ` Jay Soffian
2009-03-12 1:21 ` Jay Soffian
2009-03-15 3:28 ` John M. Dlugosz
2009-03-15 12:36 ` Jay Soffian
2009-03-16 1:07 ` John M. Dlugosz
2009-03-16 1:43 ` Jay Soffian
2009-03-15 18:33 ` 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=7vprgnlf3f.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
--cc=ngnr63q02@sneakemail.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).