From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.devel Subject: Re: Obscure error/warning/information message from git pull Date: Sat, 15 Nov 2014 08:28:31 +0100 Message-ID: <87d28o53ds.fsf@thinkpad-t440p.tsdh.org> References: <20141114120604.GA3859@acm.acm> <87389mkjwo.fsf@thinkpad-t440p.tsdh.org> <20141114141434.GM3565@embecosm.com> <20141114180521.GA3168@acm.acm> <87h9y1mwxl.fsf@igel.home> <20141114200957.GC3168@acm.acm> <878ujdmrmy.fsf@igel.home> <20141114220421.GE3168@acm.acm> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1416036535 11527 80.91.229.3 (15 Nov 2014 07:28:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 15 Nov 2014 07:28:55 +0000 (UTC) Cc: Andreas Schwab , Andrew Burgess , emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 15 08:28:50 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 1XpXmq-0002uC-R2 for ged-emacs-devel@m.gmane.org; Sat, 15 Nov 2014 08:28:48 +0100 Original-Received: from localhost ([::1]:39334 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpXmq-0005QY-EY for ged-emacs-devel@m.gmane.org; Sat, 15 Nov 2014 02:28:48 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35797) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpXmj-0005QN-SY for emacs-devel@gnu.org; Sat, 15 Nov 2014 02:28:46 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XpXmf-0005gQ-Db for emacs-devel@gnu.org; Sat, 15 Nov 2014 02:28:41 -0500 Original-Received: from out2-smtp.messagingengine.com ([66.111.4.26]:58500) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpXmf-0005gI-A2 for emacs-devel@gnu.org; Sat, 15 Nov 2014 02:28:37 -0500 Original-Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id E76F520A83 for ; Sat, 15 Nov 2014 02:28:36 -0500 (EST) Original-Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Sat, 15 Nov 2014 02:28:36 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:from:to:cc:subject:references :date:in-reply-to:message-id:mime-version:content-type; s= smtpout; bh=eZm3UgExDd+8E/orVnS1AMDU76I=; b=tw1YUj4PS2T40c4jIgXk 0YYDd3H7R8Mi8n50OWpzn+VhDyFGWr2F0E9A5w9RL2VYj9fbZ2PyXQHgMe1LwCQe a9B4jY1yq1fMiLyAc6NBbfe/TjpZ7xBYRTO+Jy1nis9y3gbK8AZodVtCRS+GkOB5 JMaG9y+xWVdLwwxF1yqIaF0= X-Sasl-enc: /QQ10aOy/6P6nh5npNmsrf6Q49j9+/a1N/h9ULDmDZyq 1416036516 Original-Received: from thinkpad-t440p.tsdh.org (unknown [2.162.47.248]) by mail.messagingengine.com (Postfix) with ESMTPA id 98DCAC0000A; Sat, 15 Nov 2014 02:28:35 -0500 (EST) Mail-Followup-To: Alan Mackenzie , Andreas Schwab , Andrew Burgess , emacs-devel@gnu.org In-Reply-To: <20141114220421.GE3168@acm.acm> (Alan Mackenzie's message of "Fri, 14 Nov 2014 22:04:21 +0000") User-Agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 66.111.4.26 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:177141 Archived-At: Alan Mackenzie writes: >> > This doesn't work very well. It prints out the information for the first >> > commit that is displayed, but no more. This feels like a git bug. > >> No, this is the correct behaviour. > > So, not very useful, then. Also not what the FM says: > > "Print out the ref names of any commits that are shown." > > . Not one commit, but any (i.e. all) commits. Of course, that's all > dependent on knowing what "ref name" means. I suppose you're going to > tell me next that only the first commit actually has a "ref name" > (whatever that is). But if you do, it would be really nice if you > could explain what is meant by "ref name", or even point me at a non > content-free definition. :-) I'd say a ref name is a name for a commit which has some special meaning. Then you can use the ref name instead of the SHA1 to operate on it. For example, HEAD is the ref name for the most recent commit in the current branch, and a branch is actually only a ref name for some commit. HEAD is called a symbolic ref because its value is a ref name again. That's what I get in the emacs-24 branch: % cat .git/HEAD .git/refs/heads/emacs-24 ref: refs/heads/emacs-24 4cd0f2dc6f868bc76c2326db1a16b3bb21f78024 And any tag is a ref name, too. When you do "git log --decorate" in the emacs-24 branch, you'll see more decorated commits, e.g.,: commit 83bad90efe943e7c88431b7a71bc1d5cf1304c92 (tag: emacs-24.4) Author: Glenn Morris Date: Mon Oct 20 20:21:15 2014 +0100 Add 24.4 release ChangeLog entries commit 9b4fdfd9b67aa9e370cd20e0188f08678daa665c (tag: emacs-24.4-rc1) Author: Glenn Morris Date: Fri Oct 17 09:08:40 2014 -0700 Regenerate ldefs-boot That's explained well in the git book at http://git-scm.com/book/en/v2/Git-Internals-Git-References HTH, Tassilo