From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Kai Germaschewski <kai-germaschewski@uiowa.edu>
Cc: Peter Chubb <peter@chubb.wattle.id.au>,
trivial@rustcorp.com.au, linux-kernel@vger.kernel.org
Subject: Re: Allow aic7xx firmware to be built from BK tree.
Date: Mon, 20 May 2002 23:07:00 -0600 [thread overview]
Message-ID: <200205210507.g4L570948949@aslan.scsiguy.com> (raw)
In-Reply-To: Your message of "Mon, 20 May 2002 23:48:56 CDT." <Pine.LNX.4.44.0205202339300.1673-100000@chaos.physics.uiowa.edu>
>On Mon, 20 May 2002, Justin T. Gibbs wrote:
>
>> >This patch removes the two generate files (that are also in the
>> >distributed kernel) before attempting to regenerate them.
>>
>> Why is this necessary?
>
>Well, I'll take Keith Owen's role and answer:
>
>Some people are using source control management systems which
>leave the managed files read-only.
These people shouldn't be rebuilding the firmware. 8-)
>Some developers use bitkeeper these days, and it'll show exactly this
>problem. I suppose the only reason that not more people complain about it
>is that hardly anyone has set CONFIG_AIC7XXX_BUILD_FIRMWARE=y.
Which is the default. Those enabling this feature get what they get
as is documented in Configure.help (or at least was in 2.4.X).
>The correct way to fix this is to not overwrite the shipped files. The
>appended patch is a suggestion on how to avoid the mentioned problems.
>(I should pay credit to Keith Owens, since he proposed a similar solution
>before)
Only with lots of MD5 junk and other complicated rules. I have no problem
with changing the name of the shipped files and using a link if that will
finally put this issue to rest.
--
Justin
next prev parent reply other threads:[~2002-05-21 5:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 1:19 Peter Chubb
2002-05-21 3:38 ` Justin T. Gibbs
2002-05-21 4:48 ` Kai Germaschewski
2002-05-21 5:07 ` Justin T. Gibbs [this message]
2002-05-21 5:20 ` Kai Germaschewski
2002-05-21 8:57 ` Peter Chubb
[not found] <mailman.1021944350.2120.linux-kernel2news@redhat.com>
2002-05-21 4:54 ` Pete Zaitcev
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=200205210507.g4L570948949@aslan.scsiguy.com \
--to=gibbs@scsiguy.com \
--cc=kai-germaschewski@uiowa.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
--cc=trivial@rustcorp.com.au \
/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®