From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-373765-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 5900 invoked by alias); 31 Jul 2014 17:57:17 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Received: (qmail 5883 invoked by uid 89); 31 Jul 2014 17:57:13 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-ie0-f178.google.com
Received: from mail-ie0-f178.google.com (HELO mail-ie0-f178.google.com) (209.85.223.178) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Thu, 31 Jul 2014 17:57:12 +0000
Received: by mail-ie0-f178.google.com with SMTP id rd18so4368570iec.9        for <gcc-patches@gcc.gnu.org>; Thu, 31 Jul 2014 10:57:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:mime-version:in-reply-to:references:date         :message-id:subject:from:to:cc:content-type;        bh=/jUC0jtnFQALqLt0jFbKRxrhUt9LIpz9vbLBMievX00=;        b=PxZ6ZQ7KaSxsB/5pP97vaYT8oMvUkScvQqxTLHtqoh+XA5CDkHaAdggCLnr0gtJta7         HSVBFSSnQnOPesIKSMACzXAwZ9CXekEELhkHh/eY45290YtrNnKiafB2uQEr2m0ikMhj         RbZkpeDHzUAIZi+jjWHa/8ml4KPFh3UyRxA2ak1CdbmgLzUJ3O5RnQsJCUY2jZO7b0Th         xVqtM7enq5lOv/7qfGKaMbNs5EchzOUuzsB27uld/6SWsY63KZsVYYeZc985aNrdbhPu         oO+L2iId1m3MaHod4i0mylOt5b3Yq9HiFqUHDHNIUbruXUhwVltmHMPXkxFNgNiePckK         ELgg==
X-Gm-Message-State: ALoCoQkJJ0CgaXFQKsWekooWz0u8/Nx+mRKc42Pdgomqxb8sW8sA4ljvpmYm0KREmySYowSb9ZFw
MIME-Version: 1.0
X-Received: by 10.50.18.82 with SMTP id u18mr164150igd.46.1406829429987; Thu, 31 Jul 2014 10:57:09 -0700 (PDT)
Received: by 10.64.239.231 with HTTP; Thu, 31 Jul 2014 10:57:09 -0700 (PDT)
In-Reply-To: <53CCD02D.3070009@samsung.com>
References: <53CCD02D.3070009@samsung.com>
Date: Thu, 31 Jul 2014 18:11:00 -0000
Message-ID: <CAD_=9DQ+-e=5WX3+TDRZrJzL1Pn2z6Vq1OOtD0d+K=LU+pCzQQ@mail.gmail.com>
Subject: Re: [PATCH] Fix mklog to support running from arbitrary folder
From: Diego Novillo <dnovillo@google.com>
To: Yury Gribov <y.gribov@samsung.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Trevor Saunders <tsaunders@mozilla.com>
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
X-SW-Source: 2014-07/txt/msg02220.txt.bz2

On Mon, Jul 21, 2014 at 4:32 AM, Yury Gribov <y.gribov@samsung.com> wrote:
> Hi all,
>
> Current mklog works only if run from GCC top-level folder. The patch allows
> running from arbitrary directory.
>
> I've used Linux directory separators which is probably ok because script
> already expects Linux environment (dirname, basename, etc.).
>
> Ok to commit?

OK.  Thanks.


Diego.