From: Willy Tarreau <w@1wt.eu>
To: michael chang <thenewme91@gmail.com>
Cc: Stephen Clark <Stephen.Clark@seclark.us>,
ck list <ck@vds.kolivas.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [ck] Re: RSDL v0.28 for 2.6.20
Date: Sat, 10 Mar 2007 23:11:50 +0100 [thread overview]
Message-ID: <20070310221150.GA6274@1wt.eu> (raw)
In-Reply-To: <b14e81f00703101356s248bd914m91c26e2d22e507d4@mail.gmail.com>
On Sat, Mar 10, 2007 at 04:56:57PM -0500, michael chang wrote:
> On 3/10/07, Willy Tarreau <w@1wt.eu> wrote:
> >BTW, Con, I think that you should base your work on 2.6.20.[23] and not
> >2.6.20 next time, due to this conflict. It will get wider adoption.
^^^^^^^^^^
> Maybe I'm naive, but I find this hard to understand -- 2.6.20.2 didn't
> exist when Con published his patch. (Con published it ~12 hours before
> the release of 2.6.20.2, from what I can tell.) How can he base his
> work on something that didn't yet exist? (And it applied cleanly to
> 2.6.20.1, the latest when he published it.)
You see the words I have underlined ? "next time". I know for sure he
published it before 2.6.20.2, but now that it is out, I suggested that
Con rebases his work on this version for new releases.
Regards,
Willy
next prev parent reply other threads:[~2007-03-10 22:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-10 7:45 RSDL v0.28 for 2.6.20 Con Kolivas
2007-03-10 18:09 ` Stephen Clark
2007-03-10 19:11 ` Willy Tarreau
2007-03-10 21:56 ` [ck] " michael chang
2007-03-10 22:11 ` Willy Tarreau [this message]
2007-03-10 22:26 ` michael chang
2007-03-10 23:54 ` Con Kolivas
2007-03-11 0:43 ` [ck] " Thibaut VARENE
2007-03-11 0:44 ` Thibaut VARENE
2007-03-10 18:15 ` RSDL v0.28 for 2.6.20 -> backport to 2.6.18.8 Fortier,Vincent [Montreal]
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=20070310221150.GA6274@1wt.eu \
--to=w@1wt.eu \
--cc=Stephen.Clark@seclark.us \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thenewme91@gmail.com \
/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.