All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair Tonner <Alistair@nerdnet.ca>
To: netfilter@lists.samba.org
Subject: problem with ./runme in --batch mode. -- current p-o-m
Date: Thu, 9 Jan 2003 22:24:00 -0500	[thread overview]
Message-ID: <200301092224.00419.Alistair@nerdnet.ca> (raw)
In-Reply-To: <200301092118.21946.netfilter@newkirk.us>


	Hi folks:
	Looking to minimize my time and general frustration levels, I set about 
automating my kernel rebuild process ... including doing the *go get kernel*, 
go patch kernel, make dep, make modules, make bzimage.... its somewhat more 
complex than that but what I found is that there is a little hook in ./runme 
if one invokes ./runme with --batch one invokes a loop at line 749 as 
follows... 

# Check to see if there is excluded patches
EXCLUDED=
while [ "$1" = "--exclude" ]; do
    EXCLUDED="$EXCLUDED $2"
    shift
    shift
done


 --- Correct me if I'm utterly off base, but does that second shift not close 
the loop by making $1 != --exclude for a long list of excluded suite/patches?

I'm trying to run this with patches I know that work (and install well) with a 
particular kernel .... and my little scripty b0rks at this and misapplies 
patches that I most definately do not want on my system ... and several that 
don't apply ... 

    Alistair Tonner
	Alistair@nerdnet.ca


  reply	other threads:[~2003-01-10  3:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <565759501.20030109180351@wp.pl>
2003-01-09 18:58 ` Kaaza 2 jammer Darrell Dieringer
2003-01-10  2:18   ` Joel Newkirk
2003-01-10  3:24     ` Alistair Tonner [this message]
2003-01-10  3:44 problem with ./runme in --batch mode. -- current p-o-m Alistair Tonner
2003-01-10 23:38 ` Arnt Karlsen

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=200301092224.00419.Alistair@nerdnet.ca \
    --to=alistair@nerdnet.ca \
    --cc=netfilter@lists.samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.