git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Vaclav Hanzl <hanzl@noel.feld.cvut.cz>,
	git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Documentation: Note about the meaning of "clone"
Date: Sun, 15 Jun 2008 15:39:17 +0200	[thread overview]
Message-ID: <200806151539.17967.jnareb@gmail.com> (raw)
In-Reply-To: <200806151505.27686.robin.rosenberg.lists@dewire.com>

Robin Rosenberg wrote:
>
> Clarify that a clone is not an exact copy.

> +*NOTE*: Although this command is called clone, the clone is not identical
> +in all respects. Local branches in the repository being cloned
> +becomes remote tracking branches in the clone and remote tracking
> +branches are not cloned at all. For security reasone the config sections
> +and triggers are not cloned either.

One nitpick, one comment, one historical comment.

Nitpick: Actually biological clone is usually not identical in
phenotype, and we know now that due to different gene expression
it can have different genotype as well. ;-)

COMMENT: when you do "git clone --bare" it mirrors local (regular)
branches in 1:1 correspondence; but it still doesn't clone anything
outside refs/heads/ and refs/remotes (and HEAD).

Historical comment: git-clone used to do 1:1 mapping even for non-bare
clone, with exception of <current branch> -> origin mapping, before
behavior provided by --use-separate-remotes was made default (thanks
Carl!).

-- 
Jakub Narebski
Poland

  reply	other threads:[~2008-06-15 13:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-14 13:05 Document clone of clone loosing branches? Vaclav Hanzl
2008-06-14 14:31 ` Jeff King
2008-06-14 20:15   ` Document clone of clone ... bug?? Vaclav Hanzl
2008-06-14 20:34     ` Jakub Narebski
2008-06-14 20:48       ` Vaclav Hanzl
2008-06-14 14:31 ` Document clone of clone loosing branches? Jakub Narebski
2008-06-14 14:44 ` Lea Wiemann
2008-06-14 21:36   ` Vaclav Hanzl
2008-06-14 22:18     ` Junio C Hamano
2008-06-15  7:18       ` Vaclav Hanzl
2008-06-14 23:03     ` Jakub Narebski
2008-06-15  8:40 ` Jakub Narebski
2008-06-15 13:05   ` [PATCH] Documentation: Note about the meaning of "clone" Robin Rosenberg
2008-06-15 13:39     ` Jakub Narebski [this message]
2008-06-15 13:52     ` Wincent Colaiuta
2008-06-15 16:31       ` Vaclav Hanzl
2008-06-15 17:03     ` Vaclav Hanzl
2008-06-15 19:12     ` Miklos Vajna
2008-06-15 20:14     ` Junio C Hamano
2008-06-15 13:05   ` PATCH] cvsimport: Clarification on the use of -r Robin Rosenberg

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=200806151539.17967.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=hanzl@noel.feld.cvut.cz \
    --cc=robin.rosenberg.lists@dewire.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).