From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: Full logical patch: and, or, subexpressions.
Date: Fri, 18 Nov 2011 02:21:36 +0100 [thread overview]
Message-ID: <20111118012136.GA16657@iris.usta.de> (raw)
In-Reply-To: <4EC521E4.8000700@bsd.lv>
Hi Kristaps,
Kristaps Dzonsons wrote on Thu, Nov 17, 2011 at 04:01:56PM +0100:
> Enclosed is a polished patch for full logical subexpressions,
This looks good, thanks!
I have merged and committed it to OpenBSD.
As expected, the conflicts were massive,
i basically did a line-by-line manual merge
without ever using patch(1) at all.
Considering the time of the night, I did only light testing,
but put it in anyway such that you have a reference merge
when merging back to bsd.lv. I'd be grateful if you could
point out all my merge errors to me... >:o)
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2011-11-18 1:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 15:01 Kristaps Dzonsons
2011-11-18 1:21 ` Ingo Schwarze [this message]
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=20111118012136.GA16657@iris.usta.de \
--to=schwarze@usta.de \
--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).