From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Achim Gratz Newsgroups: gmane.emacs.devel Subject: Re: Obscure error/warning/information message from git pull Date: Sat, 15 Nov 2014 21:48:29 +0100 Organization: Linux Private Site Message-ID: <87mw7sur4y.fsf@Rainer.invalid> 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; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1416084546 873 80.91.229.3 (15 Nov 2014 20:49:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 15 Nov 2014 20:49:06 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 15 21:49:00 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 1XpkHC-0001kI-Fd for ged-emacs-devel@m.gmane.org; Sat, 15 Nov 2014 21:48:58 +0100 Original-Received: from localhost ([::1]:41946 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpkHC-0004uB-63 for ged-emacs-devel@m.gmane.org; Sat, 15 Nov 2014 15:48:58 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58671) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpkH3-0004u2-Up for emacs-devel@gnu.org; Sat, 15 Nov 2014 15:48:56 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XpkGx-000601-L8 for emacs-devel@gnu.org; Sat, 15 Nov 2014 15:48:49 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:37833) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpkGx-0005zv-Dq for emacs-devel@gnu.org; Sat, 15 Nov 2014 15:48:43 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XpkGv-0008Se-Vu for emacs-devel@gnu.org; Sat, 15 Nov 2014 21:48:42 +0100 Original-Received: from pd9eb003d.dip0.t-ipconnect.de ([217.235.0.61]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 15 Nov 2014 21:48:41 +0100 Original-Received: from Stromeko by pd9eb003d.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 15 Nov 2014 21:48:41 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 54 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pd9eb003d.dip0.t-ipconnect.de User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.51 (gnu/linux) Cancel-Lock: sha1:OJehRQ5KnuO+gYSTa6FYtJYq4ts= 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:177251 Archived-At: Alan Mackenzie writes: > After a "git clone", the copy is not the same as the original. If you really want an exact copy of your local repository, then just make a plain copy or do a mirror clone, THis implies making it "bare" (without a work tree), so you'd then have to move things around so that you can have your work tree checked out. But you can do that, it's just that this is almost never what you want. > In particular, branches are not preserved. I don't know, as yet, what else > fails to be copied, but I have no great confidence in the documentation > to tell me. You don't want second generation clone of the Savannah repository, you want another first generation one. Again, the most efficient way to do this is to reference your already existing clone when doing it so that the actual objects are not transferred again over the net, but taken from the "master" clone. […] > This is confusing. Is it the case that branches labelled > "remotes/origin/..." are completely contained within the same repository? No, they are labels pointing to the (heads of the) corresponding branches in the upstream repository. A branch is nothing more than a label in Git, all you really need to know is the SHA1 for the branch head to (re-)create it. You could give them different names in your clone if you wanted (no, that isn't a good idea either) or drop all but master and emacs-24 branches by changing the refspecs to be fetched. You can do this with commands or (often more simply for larger changes) by just opening the config file in Emacs and writing out what it is you want Git to do with that repo. > 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? Yes, the manpage of git clone. It talks at some length about the relation of the clone to its upstream (that thing called "origin") and that should make it pretty clear that two clones will not be exactly identical if they are pointing to a different upstream. However, all the actual objects are indeed copied, so you can modify the upstream even after the fact and the next git fetch will set things up as you wanted. Go ahead and try it, copy that section about the origin in .git/config from master to emacs-24 and see for yourself. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves