From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Add a custom ./configure script
Date: Tue, 04 Jul 2006 15:50:16 +0200 [thread overview]
Message-ID: <e8drmq$8ec$1@sea.gmane.org> (raw)
In-Reply-To: 20060704004012.22639.44317.stgit@machine.or.cz
Petr Baudis wrote:
> The patch is on top of pu, that is Jakub Narebski's autoconf patch, because
> it reuses most of its infrastructure and just replaces the configure script.
If you named it for example configure.sh, then autoconf generated version,
and your by hand created version could coexist.
For now I think it would be best to move autoconf related files (configure.ac,
config.mak.in) to the contrib/autoconf/ area. Then one would be able to
compare config.mak.autogen generated by ./configure from autoconf, and
your ./configure script.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-07-04 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 0:40 [PATCH] Add a custom ./configure script Petr Baudis
2006-07-04 13:50 ` Jakub Narebski [this message]
2006-07-04 21:57 ` Petr Baudis
2006-07-05 16:46 ` Alex Riesen
-- strict thread matches above, loose matches on Subject: below --
2006-07-04 0:25 Petr Baudis
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='e8drmq$8ec$1@sea.gmane.org' \
--to=jnareb@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).