Git development
 help / color / mirror / Atom feed
From: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: efficient cloning
Date: Mon, 20 Mar 2006 17:30:19 +0100	[thread overview]
Message-ID: <200603201730.19373.Josef.Weidendorfer@gmx.de> (raw)
In-Reply-To: <7vu09tjy38.fsf@assigned-by-dhcp.cox.net>

On Monday 20 March 2006 09:54, you wrote:
>  * A new flag --use-separate-remote stops contaminating local
>    branch namespace by upstream branch names.  The upstream
>    branch heads are copied in .git/refs/remotes/ instead of

Shouldn't this be .git/refs/remotes/origin/?
Ie. different namespaces for different remotes?

Linus wanted to still be able to say "origin" which automatically
would map to "remotes/origin/master", where the name of the remote
branch (here "master") is the first mentioned in the Pull line of
the .git/remotes file in eg.

	git diff origin..master

I am not sure whether we really want "take first refspec mentioned on Pull
line", as there can be multiple tracked remote branches with their own local
developments...
Ie. I want to be able to specify: "The local development branch X is based on
the following remote branch Y , which is tracked locally as Z.".
This way, you also could warn/prohobit accidential nonsense merges because of wrong use
of "git-pull". 

Josef

  parent reply	other threads:[~2006-03-20 16:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-19 21:16 efficient cloning James Cloos
2006-03-19 22:31 ` Shawn Pearce
2006-03-19 23:18 ` Junio C Hamano
2006-03-20  0:32   ` James Cloos
2006-03-20  1:55     ` Junio C Hamano
2006-03-20  8:54       ` Junio C Hamano
2006-03-20 15:18         ` Petr Baudis
2006-03-20 21:39           ` Junio C Hamano
2006-03-20 22:41             ` Petr Baudis
2006-03-20 23:07               ` Junio C Hamano
2006-03-20 16:30         ` Josef Weidendorfer [this message]
2006-03-20 23:04           ` Junio C Hamano
2006-03-20 23:21             ` Petr Baudis
2006-03-20 23:49               ` Junio C Hamano
2006-03-21  8:19                 ` Andreas Ericsson
2006-03-21  8:42                   ` Junio C Hamano
2006-03-21  9:19                     ` Jeff King
2006-03-21  9:45                       ` Junio C Hamano
2006-03-21 11:29                         ` Petr Baudis
2006-03-21  0:26             ` Josef Weidendorfer
2006-03-21  0:57               ` Junio C Hamano
2006-03-21  8:28           ` 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=200603201730.19373.Josef.Weidendorfer@gmx.de \
    --to=josef.weidendorfer@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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