From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Reitter Newsgroups: gmane.emacs.devel Subject: Re: vc-git: workaround for "file unregistered" problem Date: Thu, 12 Nov 2009 10:57:17 -0500 Message-ID: <6095145D-CC53-45CF-8191-4B3F5A26F575@gmail.com> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1258041768 1511 80.91.229.12 (12 Nov 2009 16:02:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 12 Nov 2009 16:02:48 +0000 (UTC) Cc: Emacs development discussions To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 12 17:02:34 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1N8c7y-0005IE-Nw for ged-emacs-devel@m.gmane.org; Thu, 12 Nov 2009 17:02:31 +0100 Original-Received: from localhost ([127.0.0.1]:53862 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N8c7t-0001RP-Dc for ged-emacs-devel@m.gmane.org; Thu, 12 Nov 2009 11:02:25 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N8c3A-0004Al-7y for emacs-devel@gnu.org; Thu, 12 Nov 2009 10:57:32 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N8c35-00048H-PB for emacs-devel@gnu.org; Thu, 12 Nov 2009 10:57:31 -0500 Original-Received: from [199.232.76.173] (port=55678 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N8c35-00048A-BR for emacs-devel@gnu.org; Thu, 12 Nov 2009 10:57:27 -0500 Original-Received: from mail-yw0-f194.google.com ([209.85.211.194]:45184) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N8c34-0001Pn-Uv for emacs-devel@gnu.org; Thu, 12 Nov 2009 10:57:27 -0500 Original-Received: by ywh32 with SMTP id 32so2275513ywh.14 for ; Thu, 12 Nov 2009 07:57:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=chAyHXc/rzLceDi8qxYPOgEZ4v6GrilaxsAbVS0A02w=; b=PFxX3rz+KXeZb6fozlOft8WEdJOzDuiSDUDQ594nLumDGikDu/mdct01lU671v9Ogy GfSHuufe/w/QVgKFzcoFvqV4ScnAaX5k4wgzczjgjcbpnrtGH5cmLlc1E7CQBL4Qi+st zn8pq2xcbUIs3pegSVx1FSljEk8sOnFjoTxOU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=ifTRugC4FljlrJnaMwoviHIDKbYtaGAshi+S0bvUJJB3D5qHz8XN1G6O0zQgMpoibI 57N2q+dOH5lG1Js5oiBc/0FaleRwIfR2A0Ucjq/xtR6TdO8MarQ5FDlmbpAaCQ1UKe9e Crih3qX2N/9L1Cp6Q5BorsN8hS68DmorjL4PY= Original-Received: by 10.101.113.4 with SMTP id q4mr2881045anm.64.1258041439987; Thu, 12 Nov 2009 07:57:19 -0800 (PST) Original-Received: from cmu-365842.wv.cc.cmu.edu (CMU-365842.WV.CC.CMU.EDU [128.237.232.154]) by mx.google.com with ESMTPS id 4sm1080874ywg.43.2009.11.12.07.57.18 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 12 Nov 2009 07:57:18 -0800 (PST) In-Reply-To: X-Mailer: Apple Mail (2.1077) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:116894 Archived-At: On Nov 12, 2009, at 10:39 AM, Stefan Monnier wrote: >> Git list [1], but received no response - I'm not sure if this is a = bug >> in git. >=20 > Can you report it as a bug? OK, let's see. The git folks have been very responsive and helpful in = the past. >> Either way, specifying full paths works around the problem, and the >> patch below does that for those who encounter similar issues. >=20 > It looks acceptable, exept that, like all patches which try to work > around a problem, it should come with a corresponding comment. If only I understood the underlying problem better! I will try to do more research and check this in with an appropriate = comment.=