mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	kbuild-devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: [kbuild-devel] linux kernel conf 0.6
Date: Thu, 3 Oct 2002 13:17:30 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0210031259120.338-100000@serv> (raw)
In-Reply-To: <Pine.LNX.4.44.0209221727290.11808-100000@chaos.physics.uiowa.edu>

Hi,

(I almost forgot to reply to this one, sorry for the delay.)

On Sun, 22 Sep 2002, Kai Germaschewski wrote:

> I'm not particularly fond of these md5sum hacks. I don't think it's all
> that annoying for the developer, either, it's basically just a
> alias make="make LKC_GENPARSER=1"
>
> (Of course, you'll have to update the _shipped files eventually, but there
> isn't really any way around that either way)

Where's the problem with md5sum? If the rules are usually not visible
anyway, why do we use the _shipped postfix at all? The depencies are
hidden this way as well, so make won't even try to regenerate the file.
The developer has to remember that extra argument to get the file
regenerated, what is IMO more hacky than using md5sum.

bye, Roman


      parent reply	other threads:[~2002-10-03 11:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-16 23:16 Roman Zippel
2002-09-20  5:10 ` [kbuild-devel] " Sam Ravnborg
2002-09-22 15:24   ` Roman Zippel
2002-09-22 22:36     ` Kai Germaschewski
2002-09-22 22:41       ` Jeff Garzik
2002-09-22 22:51         ` Kai Germaschewski
2002-09-22 22:53           ` Jeff Garzik
2002-09-22 23:03             ` Kai Germaschewski
2002-09-23  1:48               ` Jeff Garzik
2002-09-22 23:07           ` Roman Zippel
2002-09-22 23:19             ` Kai Germaschewski
2002-09-22 23:30               ` Roman Zippel
2002-09-23  1:50               ` Jeff Garzik
2002-09-23 19:59       ` Sam Ravnborg
2002-10-03 11:17       ` Roman Zippel [this message]

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=Pine.LNX.4.44.0210031259120.338-100000@serv \
    --to=zippel@linux-m68k.org \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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

all inboxes | Powered by JetHome®