git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Andreas Ericsson <ae@op5.se>
Cc: "C.J. Adams-Collier" <cjac@colliertech.org>, git@vger.kernel.org
Subject: Re: configure.ac and friends could use some love
Date: Tue, 02 Jun 2009 03:16:48 -0700 (PDT)	[thread overview]
Message-ID: <m3zlcr9c0a.fsf@localhost.localdomain> (raw)
In-Reply-To: <4A24C60C.3000600@op5.se>

Andreas Ericsson <ae@op5.se> writes:
> C.J. Adams-Collier wrote:

> > with whom should I co-ordinate?
> >
> 
> git@vger and Jakub Narebski.
> 
>   git shortlog -ns -- configure.ac
> 
> would have told you as much ;-)

While it is true that I was behind adding ./configure support to git
in optional and non-intrusive way (configure.ac and config.mak.in),
mainly to be able to use %configure macro in git.spec -- which never
materialized, I lack in my opinion expertise in autoconf to be
a maintainer for those scripts.

David Syzdek offered to help or take the brunt of the work on our
autoconf corner, see e.g. this post:
  http://article.gmane.org/gmane.comp.version-control.git/111923
but he wanted help of someone whom is familiar with the interaction
between the Makefile and configure.ac... which never materialized.

Instead of git-shortlog, you should take a look at git-blame output
who is responsible for more advanced corners of configure.ac:
David M. Syzydek (GIT_CHECK_FUNC), Ben Walton (GIT_STASH_FLAGS),
Ralf Wildenhues (caching support), etc.

-- 
Jakub Narebski
Poland
ShadeHawk on #git

  reply	other threads:[~2009-06-02 10:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01 21:41 configure.ac and friends could use some love C.J. Adams-Collier
2009-06-02  6:26 ` Andreas Ericsson
2009-06-02 10:16   ` Jakub Narebski [this message]
2009-06-05 16:16     ` Ralf Wildenhues

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=m3zlcr9c0a.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=ae@op5.se \
    --cc=cjac@colliertech.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).