From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Obscure error/warning/information message from git pull Date: Sun, 16 Nov 2014 10:23:23 +0100 Organization: Organization?!? Message-ID: <87fvdjlcs4.fsf@fencepost.gnu.org> References: <20141114180521.GA3168@acm.acm> <20141114230235.GF3168@acm.acm> <87lhncoqrp.fsf@fencepost.gnu.org> <83389khn1g.fsf@gnu.org> <87h9y0omii.fsf@fencepost.gnu.org> <83vbmgg57x.fsf@gnu.org> <878ujcoj0k.fsf@fencepost.gnu.org> <20141115120506.GA3581@acm.acm> <87r3x4mszs.fsf@fencepost.gnu.org> <20141115195736.GB3378@acm.acm> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1416129853 2108 80.91.229.3 (16 Nov 2014 09:24:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 16 Nov 2014 09:24:13 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 16 10:24:06 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Xpw3x-0006vw-Hb for ged-emacs-devel@m.gmane.org; Sun, 16 Nov 2014 10:24:05 +0100 Original-Received: from localhost ([::1]:43280 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xpw3x-0004xE-3x for ged-emacs-devel@m.gmane.org; Sun, 16 Nov 2014 04:24:05 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55679) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xpw3f-0004x9-Jf for emacs-devel@gnu.org; Sun, 16 Nov 2014 04:23:53 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xpw3X-0007eW-Gg for emacs-devel@gnu.org; Sun, 16 Nov 2014 04:23:47 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:34611) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xpw3X-0007eQ-98 for emacs-devel@gnu.org; Sun, 16 Nov 2014 04:23:39 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Xpw3U-0006of-MG for emacs-devel@gnu.org; Sun, 16 Nov 2014 10:23:36 +0100 Original-Received: from x2f516dd.dyn.telefonica.de ([2.245.22.221]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 16 Nov 2014 10:23:36 +0100 Original-Received: from dak by x2f516dd.dyn.telefonica.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 16 Nov 2014 10:23:36 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 86 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: x2f516dd.dyn.telefonica.de X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:3YpfqpolD7i3YrLP0Gy3Tkfg/PA= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:177287 Archived-At: Alan Mackenzie writes: > Hello, David. > > On Sat, Nov 15, 2014 at 03:35:35PM +0100, David Kastrup wrote: >> Alan Mackenzie writes: > >> > So "git clone" is defined in terms of "clone". Looks like a recursive >> > "definition" to me - part of what "git clone" does is to "clone[s] a >> > repository". There then follows an incoherent list of the form "does >> > A, then does B, then does C, ...". > >> > What is missing is a definition of "clone". It would appear to mean >> > "make a partial copy of". > >> No. Your copy is a complete copy of everything you ask for. If you >> don't clone a particular branch, for example, by using a single-branch >> clone, that branch will not magically be in your repository. > > After a "git clone", the copy is not the same as the original. In > particular, branches are not preserved. A local branch in the source directory becomes a remote branch in the clone. Remote branches in the clone are not exported. > I don't know, as yet, what else fails to be copied, but I have no > great confidence in the documentation to tell me. > > A branch foo in a repository degrades to remotes/origin/foo when that > repository is "cloned", and, failing special action to save it, > disappears altogether in a second generation "clone". > > Thus in my repository .../emacs-24, "cloned" from .../master, the > emacs-23 branch is irretrievably lost. > > "git clone" makes a partial copy of a repository. It does not > duplicate it. "Clone", as a verb, means "duplicate"; it never means > "truncate". If you do not want the upstream of the clone to be the original, then use git clone --mirror > I chose to clone a repository. git did not do this for me. You'll find that creating a biological clone of you does not give an identical twin either. Different age, different descendency. If you want a replication, use git clone --mirror. >> Nonsense. _Everything_ you asked for is stored on your computer. >> Git does not maintain any data off-computer. > > This is confusing. Is it the case that branches labelled > "remotes/origin/..." are completely contained within the same > repository? Yes. You can create a local branch from them using git checkout -b mywhatever origin/branchname and then work on that branch, looking at its history, without once going online. If it's there at all, it is filled in. You cannot _commit_ to such remote-tracking branches stored on your computer. If you check them out, you just get a detached HEAD if you don't create a local branch tracking the remote. You can commit to a detached HEAD but that does not touch your remote branch information. There are only two ways to update the remote branch information: either by fetching. _Or_ by successfully _pushing_ to the corresponding repository in which case Git also updates its idea of it. > Is there anywhere in the git documentation, or elsewhere, which lists > what entities are preserved by "git clone", and which ones are deleted > or modified? I'd try man git-clone or git clone --help -- David Kastrup