From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ramkumar Ramachandra Subject: Re: [BUG] git_path() returns relative paths Date: Sun, 28 Jul 2013 14:54:49 +0530 Message-ID: References: <20130728050009.GA10844@lanh> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Xin Jiang , Junio C Hamano , Git List To: Duy Nguyen X-From: git-owner@vger.kernel.org Sun Jul 28 11:25:45 2013 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1V3NEW-0001JD-6y for gcvg-git-2@plane.gmane.org; Sun, 28 Jul 2013 11:25:44 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753161Ab3G1JZa (ORCPT ); Sun, 28 Jul 2013 05:25:30 -0400 Received: from mail-ob0-f173.google.com ([209.85.214.173]:55753 "EHLO mail-ob0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753021Ab3G1JZ3 (ORCPT ); Sun, 28 Jul 2013 05:25:29 -0400 Received: by mail-ob0-f173.google.com with SMTP id er7so7240475obc.4 for ; Sun, 28 Jul 2013 02:25:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=kFAwdv4A/0Kf1+dGwRFBXtXgPyNMxtiYHdqXNAujFzo=; b=FIFvgd2weSqMmKMJYbca84Qvwtj3CGIsdaePX4pSbk50DeLX4r1gDKfuAXL7+CuNPL CiPCbwA+04xQon8YQOqRVnM+loBFnTvb+BxdhbVloa51CqwJ3gcudQH2Nk25PLKhW1k+ /gXBOTA29j6YMo6JXnagURFUfAVTkOUOqOSxXHo2wbrsCjjLbuoLuWG/X5eD9/3oHwaI 3rwLJJFta34pvVTm+QCHOAjIkDlBZQVsoSFBNfH0UOP65HbDTLB/qkrQ2/QJ5ET/N+ft ObSp7OyHX9cjyVZDu5yUJhC1w2dDPAUCxbOpMIfHpp+YdbXvXBjp/6VEbSU7j7ta7lpp mCKg== X-Received: by 10.50.6.16 with SMTP id w16mr566307igw.29.1375003529295; Sun, 28 Jul 2013 02:25:29 -0700 (PDT) Received: by 10.64.37.130 with HTTP; Sun, 28 Jul 2013 02:24:49 -0700 (PDT) In-Reply-To: <20130728050009.GA10844@lanh> Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Duy Nguyen wrote: > How about something like this as a workaround for emacs? Even if we do manage to patch Emacs now, we still need to support older versions: so yeah, this is an urgent candidate for maint. I'm waiting for the word from Emacs-Devel before writing out a commit message.