From: Arnt Karlsen <arnt@c2i.net>
To: netfilter@lists.netfilter.org
Subject: Re: problem with ./runme in --batch mode. -- current p-o-m
Date: Sat, 11 Jan 2003 00:38:07 +0100 [thread overview]
Message-ID: <20030111003807.276f2728.arnt@c2i.net> (raw)
In-Reply-To: <200301092244.09844.Alistair@nerdnet.ca>
On Thu, 9 Jan 2003 22:44:09 -0500,
Alistair Tonner <Alistair@nerdnet.ca> wrote in message
<200301092244.09844.Alistair@nerdnet.ca>:
>
> Hi folks:
>
> Its too late at night, and I shouldn't be mucking with scripts.
> ... I realize now that my previous email was in error ... and
> now realize what is actually happening when passing a long list to
> ./runme ... its just disconcerting to see patches that I don't want in
> the "already applied" list that ./runme spits up when running in batch
> mode ... I can now see that the $EXCLUDED are copied to $SEEN and
> listed in already applied list because of that ...
>
> perhaps we could put a *bypassed* tag in there so that others don't
> get as confused as I.....
..on finishing a batch run, it would be nice finding
a batch run log somewhere, to ease my confusion some,
on what works and not.
..does anyone run p-o-m from rpmbuild at all?
--
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
next prev parent reply other threads:[~2003-01-10 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 3:44 problem with ./runme in --batch mode. -- current p-o-m Alistair Tonner
2003-01-10 23:38 ` Arnt Karlsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-09 18:58 Kaaza 2 jammer Darrell Dieringer
2003-01-10 2:18 ` Joel Newkirk
2003-01-10 3:24 ` problem with ./runme in --batch mode. -- current p-o-m Alistair Tonner
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=20030111003807.276f2728.arnt@c2i.net \
--to=arnt@c2i.net \
--cc=netfilter@lists.netfilter.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.