From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Sergey Organov Newsgroups: gmane.emacs.devel Subject: Re: Obscure error/warning/information message from git pull Date: Tue, 18 Nov 2014 20:58:15 +0300 Message-ID: References: <20141114120604.GA3859@acm.acm> <87389mkjwo.fsf@thinkpad-t440p.tsdh.org> <20141114141434.GM3565@embecosm.com> <20141114180521.GA3168@acm.acm> <20141114230235.GF3168@acm.acm> <20141117141123.GA4294@acm.acm> <83lhn89zxn.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1416333634 28970 80.91.229.3 (18 Nov 2014 18:00:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 18 Nov 2014 18:00:34 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 18 19:00:27 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 1Xqn4i-0006m4-Q9 for ged-emacs-devel@m.gmane.org; Tue, 18 Nov 2014 19:00:24 +0100 Original-Received: from localhost ([::1]:54593 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xqn4i-00042K-HS for ged-emacs-devel@m.gmane.org; Tue, 18 Nov 2014 13:00:24 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45321) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xqn4X-0003yv-Fu for emacs-devel@gnu.org; Tue, 18 Nov 2014 13:00:20 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xqn4Q-0002hd-5A for emacs-devel@gnu.org; Tue, 18 Nov 2014 13:00:13 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:58200) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xqn4P-0002fQ-VX for emacs-devel@gnu.org; Tue, 18 Nov 2014 13:00:06 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Xqn2r-0005sT-Na for emacs-devel@gnu.org; Tue, 18 Nov 2014 18:58:29 +0100 Original-Received: from 89.175.180.246 ([89.175.180.246]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 18 Nov 2014 18:58:29 +0100 Original-Received: from sorganov by 89.175.180.246 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 18 Nov 2014 18:58:29 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 72 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 89.175.180.246 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) 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:177615 Archived-At: Eli Zaretskii writes: >> From: Sergey Organov >> Date: Tue, 18 Nov 2014 19:59:51 +0300 >> >> My point is that once you send "branch" to a Git command > > You don't send a branch to Git commands, you send the branch's > _label_, or _name_. Let's distinguish between the thing and its name, > okay? Yes, you send a _name_. It does not represent "branch" the "active line of development" though. It just points to particular commit. > >> Git itself has no "branches" that are "active lines of development" >> in its data model. > > Git might not have it, but we its users do. You are welcome to have them. In your mind. This won't help you to understand Git better. It's the latter that I've tried to help to achieve. Sorry if I failed. > >> Understanding this makes it clear why you need to say something like this: >> >> $ git log --source emacs-24 origin/master >> >> to get "list of commits with branch names", where: > > What's to understand? Why it is not: $ git log --show-branch-names emacs-24 origin/master > a branch name in this context represents its last commit, a.k.a. > "tip".That's all. Why are you trying to make this more confusing than > it should be? My point is that branch name doesn't represent anything else but particular reference to particular commit in Git. >> --source >> Print out the ref name given on the command line by which each >> commit was reached. >> >> Please notice no "branch" in the description of the "--source" > > I'd suggest not to treat Git docs as a kind of "holy scripture" whose > exact wording has any magic meaning beyond what meets the eye. Don't > look for some deep meaning in the words used there, because more often > than not there isn't any. The description in the docs is very exact. Sorry you don't see it, that means I'm not very good at explaining it indeed. BTW, Emacs docs are no less a "holy scripture" as well, until you start to at least remotely understand the whole picture. > >> Kinda like "everything is a buffer" in Emacs. > > But everything is not a buffer in Emacs. There are other objects as > well, most of them quite different from buffers. Sure, there are other objects but refs in Git as well, but all the refs are as similar as possible, be them branches or not. -- Sergey.