All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann Dirson <ydirson@altern.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Phil Richards <news@derived-software.ltd.uk>, git@vger.kernel.org
Subject: Re: Autoconf/Automake
Date: Fri, 16 Jun 2006 22:17:15 +0200	[thread overview]
Message-ID: <20060616201715.GM7766@nowhere.earth> (raw)
In-Reply-To: <Pine.LNX.4.63.0606160053560.7480@wbgn013.biozentrum.uni-wuerzburg.de>

On Fri, Jun 16, 2006 at 12:58:30AM +0200, Johannes Schindelin wrote:
> > On Thu, Jun 15, 2006 at 10:42:40PM +0200, Johannes Schindelin wrote:
> > > As for now, I fail to see why the current system is not adequate for git!
> > 
> > I can reassure you, gazillions of people still fail to see why cvs is
> > not adequate for their project.  And the ratio of devs in the
> > corporate world not knowning git to those not knowning cvs is far
> > superior to 2.  And everyone here knows cvs is not more adequate than
> > git for so many tasks :)
> 
> You know as well as I that this comparison is unfair. I am _NOT_ a 
> corporate person. I hope that you do not judge me as a complete airhead.

Well, I have to apologize - especially after looking closer at the
current Makefile.  I think I understand now why autoconf was suggested
in the first place, but it what it would achieve would mostly moving
the ifdef's to configure.ac, which would not be such a gain anyway.

Best regards,
-- 
Yann Dirson    <ydirson@altern.org> |
Debian-related: <dirson@debian.org> |   Support Debian GNU/Linux:
                                    |  Freedom, Power, Stability, Gratis
     http://ydirson.free.fr/        | Check <http://www.debian.org/>

  reply	other threads:[~2006-06-16 20:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14 22:27 Autoconf/Automake Pavel Roskin
2006-06-14 22:45 ` Autoconf/Automake Linus Torvalds
2006-06-14 22:54 ` Autoconf/Automake Bertrand Jacquin
2006-06-14 23:18 ` Autoconf/Automake Timo Hirvonen
2006-06-15  7:24 ` Autoconf/Automake Yann Dirson
2006-06-15 13:31   ` Autoconf/Automake Alex Riesen
2006-06-15 16:32     ` Autoconf/Automake Yann Dirson
2006-06-15 17:02       ` Autoconf/Automake Linus Torvalds
2006-06-15 17:48         ` Autoconf/Automake Olivier Galibert
2006-06-15 18:03           ` Autoconf/Automake Jakub Narebski
2006-06-15 18:19             ` Autoconf/Automake Olivier Galibert
2006-06-16 18:23             ` Autoconf/Automake Petr Baudis
2006-06-16  9:06           ` Autoconf/Automake Jerome Lovy
2006-06-15 20:17         ` Autoconf/Automake Yakov Lerner
2006-06-15 21:14         ` Autoconf/Automake Yann Dirson
2006-06-15 22:54           ` Autoconf/Automake Linus Torvalds
2006-06-15 23:10             ` Autoconf/Automake Johannes Schindelin
2006-06-16  6:51               ` Autoconf/Automake Nikolai Weibull
2006-06-15 20:10     ` Autoconf/Automake Phil Richards
2006-06-15 20:32       ` Autoconf/Automake Timo Hirvonen
2006-06-15 20:42       ` Autoconf/Automake Johannes Schindelin
2006-06-15 22:05         ` Autoconf/Automake Yann Dirson
2006-06-15 22:58           ` Autoconf/Automake Johannes Schindelin
2006-06-16 20:17             ` Yann Dirson [this message]
2006-06-16 20:42               ` Autoconf/Automake Petr Baudis
2006-06-16 18:31           ` Autoconf/Automake 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=20060616201715.GM7766@nowhere.earth \
    --to=ydirson@altern.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=news@derived-software.ltd.uk \
    /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.