From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Subject: Re: rew_dohalt reorg and bad block-nesting bug
Date: Tue, 29 Jun 2010 11:18:41 +0200 [thread overview]
Message-ID: <4C29BA71.3040704@bsd.lv> (raw)
In-Reply-To: <20100629050626.GH31959@iris.usta.de>
Ingo, you beat me to cleaning out the rew functions--good. Those are
throwbacks from when parse rules were still changing under my feet.
> Currently, i'm not quite sure in which order to proceed. Maybe
> 1) sync
> 2) tag
Let me know when this is done; I'll hold off on further changes until
then. I expect you awake at 06:00 to respond. ;-)
> 3) merge badly nested blocks without the bugfix and reorg
> 4) merge the reorg without the bugfix
> 5) finish the .Nm/SYNOPSIS indentation stuff
> 6) look at the double-breaking bug
That's fine. My biggest concern is (3) and (4). Get them in and we'll
test them thoroughly. Then proceed from there.
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-06-29 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100627001247.GB2850@iris.usta.de>
2010-06-27 23:47 ` Back-block nesting patch Kristaps Dzonsons
2010-06-28 19:02 ` Ingo Schwarze
2010-06-28 19:26 ` Kristaps Dzonsons
2010-06-29 5:06 ` rew_dohalt reorg and bad block-nesting bug Ingo Schwarze
2010-06-29 9:18 ` Kristaps Dzonsons [this message]
2010-06-29 18:33 ` Ingo Schwarze
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=4C29BA71.3040704@bsd.lv \
--to=kristaps@bsd.lv \
--cc=tech@mdocml.bsd.lv \
/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;
as well as URLs for NNTP newsgroup(s).