public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Giacomo Catenazzi <cate@debian.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CML2-2.1.3 is available
Date: Tue, 22 Jan 2002 11:09:14 +0100	[thread overview]
Message-ID: <3C4D3A4A.6020603@debian.org> (raw)
In-Reply-To: <fa.d4sn1fv.b78io8@ifi.uio.no> <fa.i3p6mlv.1mg2frl@ifi.uio.no>


Keith Owens wrote:

> On Tue, 22 Jan 2002 10:11:10 +0100, 
> Giacomo Catenazzi <cate@debian.org> wrote:
> 
>>If autoconfigure will go in the kernel, I have not problems on
>>filenames, but when I initially created it, I thinked ev. to
>>distribuite it as a package. Here the name matter.
>>
>>IMHO longer filename ia a good things (iff normal user should
>>not type it).
>>
> 
> autoconf autoconfigure: symlinks
>         $(CONFIG_SHELL) scripts/....
> 
> make autoconf == make autoconfigure.
> 
> Watch out for the generated autoconf.h file, it might confuse some
> people.
> 


Where?

I don't find it in:
http://lxr.linux.no/search?v=2.4.17&string=autoconfigure

	giacomo


       reply	other threads:[~2002-01-22 10:12 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.d4sn1fv.b78io8@ifi.uio.no>
     [not found] ` <fa.i3p6mlv.1mg2frl@ifi.uio.no>
2002-01-22 10:09   ` Giacomo Catenazzi [this message]
2002-01-22 10:25     ` CML2-2.1.3 is available Keith Owens
2002-01-22 10:48       ` Giacomo Catenazzi
2002-01-22 10:53         ` Keith Owens
2002-01-22  9:11 [kbuild-devel] " Giacomo Catenazzi
2002-01-22  9:20 ` Keith Owens
  -- strict thread matches above, loose matches on Subject: below --
2002-01-15 19:53 Eric S. Raymond
2002-01-15 20:15 ` Nicolas Pitre
2002-01-15 20:18   ` Eric S. Raymond
2002-01-15 20:41     ` Nicolas Pitre
2002-01-15 19:19       ` Rob Landley
2002-01-16  3:48         ` Eric S. Raymond
2002-01-16  6:29           ` Peter Samuelson
2002-01-16  6:32             ` Eric S. Raymond
2002-01-16  7:13               ` Peter Samuelson
2002-01-16  6:36             ` Alexander Viro
2002-01-16  0:15     ` Henning P. Schmiedehausen
2002-01-15 20:16 ` Anton Altaparmakov
2002-01-15 20:24   ` Eric S. Raymond
2002-01-15 19:30     ` Rob Landley
2002-01-16  3:58       ` Eric S. Raymond
2002-01-15 20:25 ` Russell King
2002-01-15 19:37   ` Rob Landley
2002-01-17  1:18     ` Val Henson
2002-01-21 16:22     ` Daniel Phillips
2002-01-16  0:38   ` Peter Samuelson
2002-01-15 20:26 ` Ross Vandegrift
2002-01-16  4:02   ` Eric S. Raymond
2002-01-16 16:38     ` Ross Vandegrift
2002-01-16 16:59       ` Ross Vandegrift
2002-01-16 18:29       ` Rob Landley
2002-01-18 18:32     ` Ross Vandegrift
2002-01-22  5:31       ` Eric S. Raymond
2002-01-15 20:27 ` Robert Love
2002-01-15 21:09 ` David Lang
2002-01-16 15:06 ` Horst von Brand
2002-01-16 21:31   ` Eric S. Raymond
2002-01-16 21:56     ` Horst von Brand
2002-01-16 21:47       ` Eric S. Raymond
2002-01-17  1:26       ` David Woodhouse
2002-01-17  1:43         ` Eric S. Raymond
2002-01-17  8:53         ` David Woodhouse
2002-01-17 13:37           ` Eric S. Raymond
2002-01-17 14:09           ` David Woodhouse
2002-01-17 14:29             ` Eric S. Raymond
2002-01-16 23:36     ` David Lang
2002-01-18  6:48       ` Kai Henningsen

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=3C4D3A4A.6020603@debian.org \
    --to=cate@debian.org \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@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