From: SungHyun Nam <goweol@gmail.com>
To: git@vger.kernel.org
Cc: namsh@posdata.co.kr, git@vger.kernel.org, sverre@rabbelier.nl,
namsh@posdata.co.kr
Subject: Re: [PATCH] Use SHELL_PATH
Date: Thu, 17 Jul 2008 09:38:56 +0900 [thread overview]
Message-ID: <487E94A0.1040801@gmail.com> (raw)
In-Reply-To: <487E932A.5080502@gmail.com>
SungHyun Nam wrote:
> And I also need to run a script function below between 'make all'
> and 'make test/install'. I hope GIT does this. Of course, GIT's
> Makefile would use SHELL_PATH and PERL_PATH.
Oops! I'm sorry! Ignore this part. GIT alreay does it, just i didn't
realize that.
Regards,
namsh
prev parent reply other threads:[~2008-07-17 0:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 1:31 [PATCH] Use SHELL_PATH SungHyun Nam
2008-07-16 10:47 ` Sverre Rabbelier
2008-07-16 11:00 ` Johannes Schindelin
2008-07-16 15:46 ` Junio C Hamano
2008-07-16 16:05 ` Junio C Hamano
2008-07-17 0:32 ` SungHyun Nam
2008-07-17 0:38 ` SungHyun Nam [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=487E94A0.1040801@gmail.com \
--to=goweol@gmail.com \
--cc=git@vger.kernel.org \
--cc=namsh@posdata.co.kr \
--cc=sverre@rabbelier.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.