From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] build: generate test scripts
Date: Fri, 07 Jun 2013 16:12:17 -0700 [thread overview]
Message-ID: <7vobbhqzvy.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAMP44s3doQe2PTGSbZ7Afi9DNDGstN4VJAompeLxUjn4Cg=g2Q@mail.gmail.com> (Felipe Contreras's message of "Fri, 7 Jun 2013 17:43:43 -0500")
Felipe Contreras <felipe.contreras@gmail.com> writes:
> It is generated, in next. If it's not generated, there's no need to
> add it to NO_INSTALL.
OK, that makes sense.
Thanks.
next prev parent reply other threads:[~2013-06-07 23:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 22:03 [PATCH 0/2] Build fixes Felipe Contreras
2013-06-07 22:03 ` [PATCH 1/2] build: generate test scripts Felipe Contreras
2013-06-07 22:06 ` Felipe Contreras
2013-06-07 22:28 ` Junio C Hamano
2013-06-07 22:33 ` Felipe Contreras
2013-06-07 22:40 ` Junio C Hamano
2013-06-07 22:43 ` Felipe Contreras
2013-06-07 23:12 ` Junio C Hamano [this message]
2013-06-07 22:03 ` [PATCH 2/2] build: do not install git-remote-testgit Felipe Contreras
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=7vobbhqzvy.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
/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 NNTP newsgroup(s).