git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: George Spelvin <linux@horizon.com>, git@vger.kernel.org
Subject: Re: [1.8.0] reorganize the mess that the source tree has become
Date: Thu, 03 Feb 2011 19:01:34 +0100	[thread overview]
Message-ID: <m2fws5m1z5.fsf@igel.home> (raw)
In-Reply-To: <alpine.LFD.2.00.1102030036420.12104@xanadu.home> (Nicolas Pitre's message of "Thu, 03 Feb 2011 01:16:10 -0500 (EST)")

Nicolas Pitre <nico@fluxnic.net> writes:

> This has _nothing_ about any autoconf convention.  GNU autoconf requires 
> stupid things like having a bunch of files such as CREDITS, INSTALL, 
> CHANGELOG, and other whatnots even if you have nothing to put in them, 
> in which case they still have to be there but empty.  It also dictates 
> the exact name your directories must have, etc.

That's automake, not autoconf (and only the default automake operation).

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  parent reply	other threads:[~2011-02-03 18:01 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02  2:29 [1.8.0] reorganize the mess that the source tree has become George Spelvin
2011-02-02  8:31 ` Erik Faye-Lund
2011-02-02 20:01   ` Pascal Obry
2011-02-03  6:16 ` Nicolas Pitre
2011-02-03  8:09   ` Miles Bader
2011-02-03 18:01   ` Andreas Schwab [this message]
2011-02-03 18:46   ` Eugene Sajine
2011-02-03 21:42     ` Hilco Wijbenga
2011-02-04  2:06       ` Miles Bader
2011-02-04  8:30         ` Tor Arntsen
2011-02-04 10:49           ` Jakub Narebski
2011-02-04 11:17         ` Erik Faye-Lund
2011-02-04 18:15         ` [1.8.0] " Nicolas Sebrecht
2011-02-04 22:47           ` Drew Northup
2011-02-05 15:11             ` Nicolas Sebrecht
  -- strict thread matches above, loose matches on Subject: below --
2011-01-31  5:53 What's cooking in git.git (Jan 2011, #06; Sun, 30) Junio C Hamano
2011-01-31 17:05 ` Planning for 1.7.5 and 1.8.0 Junio C Hamano
2011-01-31 20:28   ` [1.8.0] reorganize the mess that the source tree has become Nicolas Pitre
2011-01-31 20:57     ` Junio C Hamano
2011-01-31 21:08       ` Matthieu Moy
2011-01-31 21:33         ` Nicolas Pitre
2011-01-31 21:19       ` Nicolas Pitre
2011-01-31 21:00     ` Jeff King
2011-01-31 21:28       ` Nicolas Pitre
2011-01-31 22:17         ` Junio C Hamano
2011-01-31 22:36           ` João P. Sampaio
2011-01-31 22:37           ` Nicolas Pitre
2011-01-31 23:12         ` Jeff King
2011-02-01  0:29           ` Nicolas Pitre
2011-02-01  1:48             ` Jeff King
2011-02-01  4:05               ` Nicolas Pitre
2011-02-01 12:42                 ` Thomas Rast
2011-02-01 11:14                   ` Jonathan Nieder
2011-02-01 11:22                     ` Jonathan Nieder
2011-02-01 13:08                   ` Nicolas Pitre
2011-02-01 16:02                   ` Nguyen Thai Ngoc Duy
2011-02-01 21:53               ` Junio C Hamano
2011-02-01  0:35           ` Erik Faye-Lund
2011-02-01  1:53             ` Jeff King
2011-02-01  1:00           ` Sverre Rabbelier
2011-02-01  1:57             ` Jeff King
2011-02-01  7:24           ` Jay Soffian
2011-02-01 14:42         ` Andreas Ericsson
2011-02-05  3:21     ` Martin von Zweigbergk

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=m2fws5m1z5.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=git@vger.kernel.org \
    --cc=linux@horizon.com \
    --cc=nico@fluxnic.net \
    /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).