linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: "Cristian Rodríguez" <crrodriguez@opensuse.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] lib/ext2fs/bitops.h: Use the optmized/documented byteswapping routines
Date: Mon, 14 Jan 2013 16:56:22 -0500	[thread overview]
Message-ID: <20130114215622.GA24179@thunk.org> (raw)
In-Reply-To: <50F4254B.9040102@opensuse.org>

On Mon, Jan 14, 2013 at 12:33:31PM -0300, Cristian Rodríguez wrote:
> On 01/14/2013 11:20 AM, Theodore Ts'o wrote:
> 
> >why bother using autoconf and automake
> 
> For a very simple reason, fixing hand written makefiles is the
> number 1 burden in distribution mainteniance.
> 
> Any autotools stuff provided is always better and causes less pain
> than ad-hoc build scripts.

Maybe for distribution people (although I haven't had that many
complaints with my hand-written Makefile.in files).  But automake
causes ***huge*** amounts of pain for developers, especially when they
want to run binaries out of the build tree for debugging purposes or
for regression testing.

I hate automake almost as much as I dispise GNOME 3.

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-01-14 21:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-12 19:32 [PATCH] lib/ext2fs/bitops.h: Use the optmized/documented byteswapping routines Cristian Rodríguez
2013-01-14 14:13 ` Theodore Ts'o
2013-01-14 14:20   ` Theodore Ts'o
2013-01-14 15:33     ` Cristian Rodríguez
2013-01-14 21:56       ` Theodore Ts'o [this message]
2013-01-15  1:07   ` Cristian Rodríguez
2013-01-15  2:05     ` Theodore Ts'o

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=20130114215622.GA24179@thunk.org \
    --to=tytso@mit.edu \
    --cc=crrodriguez@opensuse.org \
    --cc=linux-ext4@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).