From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: Bugs and regressions in .Bk
Date: Mon, 7 Feb 2011 00:07:13 +0100 [thread overview]
Message-ID: <20110206230713.GK28747@iris.usta.de> (raw)
In-Reply-To: <4D4F169C.2030800@bsd.lv>
Hi Kristaps,
Kristaps Dzonsons wrote on Sun, Feb 06, 2011 at 10:46:04PM +0100:
> On 06/02/2011 21:39, Ingo Schwarze wrote:
>> So, my plan is to
>>
>> 1) Get the following patch in, fixing the latter bug - OK?
>> The code is unchanged, it is just moved around.
>>
>> 2) Once that's in, merge your patch to OpenBSD, together
>> with my fix for the regression.
>>
>> 3) Finally, merge back my regression fix to bsd.lv.
> That's fine by me. I haven't closely examined the behaviour, but it
> looks reasonable.
Thanks for having a look!
All three steps are now done in both repositories.
> Please add in the necessary comments in the code
> as to why the order is important, though...
That comment is in place, too.
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2011-02-06 23:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201101251620.p0PGKPeH004751@krisdoz.my.domain>
2011-02-06 20:39 ` Ingo Schwarze
2011-02-06 21:46 ` Kristaps Dzonsons
2011-02-06 23:07 ` 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=20110206230713.GK28747@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).