From: Theodore Tso <tytso@mit.edu>
To: Junio C Hamano <junkio@cox.net>
Cc: Luben Tuikov <ltuikov@yahoo.com>, git@vger.kernel.org
Subject: Re: New way of tracking remote branches -- question
Date: Sat, 6 Jan 2007 09:10:32 -0500 [thread overview]
Message-ID: <20070106141032.GB28972@thunk.org> (raw)
In-Reply-To: <7v8xghariv.fsf@assigned-by-dhcp.cox.net>
On Fri, Jan 05, 2007 at 05:11:04PM -0800, Junio C Hamano wrote:
> * Your heads/ namespace is of your own. The repository clone
> sets up arranges the master branch to start from the same
> commit as where you cloned from, and sets up so that changes
> made on the master at the remote is merged into your master,
> but that is merely a convention that was deemed as the most
> common and the most convenient.
The other nice thing about the new scheme is that if new branches
appear in the remote repository, they automatically show up in
remote/origin/*. Before, if new branches showed up after the initial
clone, you'd never know about it and it wouldn't be possible to
automatically create new branches in heads/ since it might conflict
with an originally existing branch in the local namespace. So IMHO,
the separation of namespace is definitely a good thing.
- Ted
next prev parent reply other threads:[~2007-01-06 14:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 23:02 New way of tracking remote branches -- question Luben Tuikov
2007-01-05 23:17 ` Junio C Hamano
2007-01-05 23:39 ` Junio C Hamano
2007-01-06 0:39 ` Luben Tuikov
2007-01-06 0:16 ` Luben Tuikov
2007-01-05 23:50 ` Junio C Hamano
2007-01-06 1:11 ` Junio C Hamano
2007-01-06 2:11 ` Steven Grimm
2007-01-06 14:10 ` Theodore Tso [this message]
2007-01-09 7:45 ` Luben Tuikov
2007-01-09 8:28 ` Junio C Hamano
2007-01-09 8:41 ` Luben Tuikov
2007-01-09 8:57 ` Martin Langhoff
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=20070106141032.GB28972@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=ltuikov@yahoo.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).