>>>>> "Binand" == Binand Raj S <[EMAIL PROTECTED]> writes:
Binand> On Sunday 24 February 2002 3:06 am, Mayuresh Kathe wrote:
>> So in that case, instead of typing out 'bzcat patchname | patch
>> -p0' ten times, it would be easier to run a script which does
>> everything for you.
Binand> The problem with this approach is error recovery. If one
Binand> of the intermediate patches didn't apply cleanly and if
Binand> the script didn't handle this, you will end up with a
Binand> horribly broken kernel tree.
Been using patch-kernel for the past 8 years and the `horribly broken
kernel' hasn't happened yet. BTW, I compile all my kernels by hand,
so it's not that I compile/patch one kernel a year.
Patch-kernel automatically detects if the patch(es) went off OK,
cleans up after itself, and stops if there're any errors. Not much
scope for breaking the source there.
Binand> Scripts are OK for day to day activities, but not for
Binand> things related to the kernel, IMO. With bash's command
Binand> history and readline editing, you don't gain much with a
Binand> script. IMO, if there is no control flow involved, there
Binand> is no need for a shell script either.
I'd say using the script for this is safer than doing it by hand. You
do gain cleanliness, and most important, time. Don't forget the three
top virtues of a good programmer: laziness, impatience and hubris;
even if you aren't a programmer, it wouldn't hurt to emulate one once
in a while :-)
Regards,
-- Raju
--
Raju Mathur [EMAIL PROTECTED] http://kandalaya.org/
It is the mind that moves
_______________________________________________
linux-india-help mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/linux-india-help
