From: Lea Wiemann <lewiemann@gmail.com>
To: Vaclav Hanzl <hanzl@noel.feld.cvut.cz>
Cc: git@vger.kernel.org
Subject: Re: Document clone of clone loosing branches?
Date: Sat, 14 Jun 2008 16:44:55 +0200 [thread overview]
Message-ID: <4853D967.5080903@gmail.com> (raw)
In-Reply-To: <20080614.150548.71104932.hanzl@noel.feld.cvut.cz>
Vaclav Hanzl wrote:
> with naive belief that clone is a 1:1 copy or something close,
> nasty surprise can happen:
I got bitten by that, too. Perhaps the intro paragraph of git-clone.txt
(man git-clone) could mention that remote branches are not cloned or so.
(I don't know git-clone well enough to be able to phrase it
accurately, but perhaps someone else wants to send a documentation patch...)
-- Lea
next prev parent reply other threads:[~2008-06-14 14:45 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 [this message]
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
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=4853D967.5080903@gmail.com \
--to=lewiemann@gmail.com \
--cc=git@vger.kernel.org \
--cc=hanzl@noel.feld.cvut.cz \
/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).