From: Tomas Szepe <szepe@pinerecords.com>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19-pre9-ac1
Date: Thu, 30 May 2002 19:09:21 +0200 [thread overview]
Message-ID: <20020530170921.GF7078@louise.pinerecords.com> (raw)
In-Reply-To: <200205301311.g4UDBlY21108@devserv.devel.redhat.com>
So what's the secret behind -pre9-ac2? :)
T.
> [+ indicates stuff that went to Marcelo, o stuff that has not,
> * indicates stuff that is merged in mainstream now, X stuff that proved
> bad and was dropped out]
>
> Linux 2.4.19pre9-ac1
> o Merge with 2.4.19pre9
> o Fix SuS violation on readv/writev (me)
> | I believe this one is correct, please double check
> ...
next prev parent reply other threads:[~2002-05-30 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 13:11 Linux 2.4.19-pre9-ac1 Alan Cox
2002-05-30 17:09 ` Tomas Szepe [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-30 17:45 Marc-Christian Petersen
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=20020530170921.GF7078@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox