linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: Generated files in e2fsprogs git repo
Date: Mon, 30 Jun 2014 21:02:50 -0400	[thread overview]
Message-ID: <20140701010250.GA23932@thunk.org> (raw)
In-Reply-To: <CAJTo0LYeerPnHpaxAw36N7BiWH4PKUMAX=1j+Szc7J9zvB7jjw@mail.gmail.com>

On Mon, Jun 30, 2014 at 05:52:29PM +0100, Burton, Ross wrote:
> 
> Would anyone object to a patch set to remove all generated files
> (aclocal.m4, configure, intl/*, po/Makefile.in.in, etc) from the
> e2fsprogs git repository?  They'll still exist in tarballs, but anyone
> building from git would need to run autoreconf to regenerate them -
> the plus side being that the shipped aclocal.m4 won't be forcing
> archaic macros onto users.


I don't trust autoreconf.  Different versions of autoconf can end up
with different incompatible versions of autoconf macros, and I have
seen some rather disastrous failures as a result.  That's why I update
autoconf under my control, and if you run autoreconf as a user, and it
breaks because the "archaic macros" work, and the "new shiny" macros
fail, that's your problem, and I will laugh at you....

      	     	  	       	      - Ted

  reply	other threads:[~2014-07-01  1:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30 16:52 Generated files in e2fsprogs git repo Burton, Ross
2014-07-01  1:02 ` Theodore Ts'o [this message]
2014-07-01  9:55   ` Burton, Ross
2014-07-01 15:22     ` 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=20140701010250.GA23932@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=ross.burton@intel.com \
    /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).