public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Yury Gribov <y.gribov@samsung.com>
To: Diego Novillo <dnovillo@google.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Trevor Saunders <tsaunders@mozilla.com>
Subject: Re: [PATCH] Fix mklog to support running from arbitrary folder
Date: Fri, 01 Aug 2014 04:22:00 -0000	[thread overview]
Message-ID: <53DB15F6.8090303@samsung.com> (raw)
In-Reply-To: <CAD_=9DQ+-e=5WX3+TDRZrJzL1Pn2z6Vq1OOtD0d+K=LU+pCzQQ@mail.gmail.com>

On 07/31/2014 09:57 PM, Diego Novillo wrote:
>> 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.

Done, r213401.

-Y

      reply	other threads:[~2014-08-01  4:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21  8:50 Yury Gribov
2014-07-28  6:42 ` [PATCH][PING] " Yury Gribov
2014-07-31 18:11 ` [PATCH] " Diego Novillo
2014-08-01  4:22   ` Yury Gribov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53DB15F6.8090303@samsung.com \
    --to=y.gribov@samsung.com \
    --cc=dnovillo@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tsaunders@mozilla.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).