From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jan Kara <jack@suse.cz>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: -- END OF BLOCK --
Date: 14 Jul 2003 19:42:19 +0100 [thread overview]
Message-ID: <1058208131.561.100.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030714174115.GA8620@atrey.karlin.mff.cuni.cz>
On Llu, 2003-07-14 at 18:41, Jan Kara wrote:
> just into the last 2.5 kernel so it's not Christophs fault he didn't
> send them to you. Actually I just wanted to send them to you myself today...
> Anyway now it seems everything is sorted out.
Yes I think so. Its also somewhat cleaner than the older -ac code which is
nice.
prev parent reply other threads:[~2003-07-14 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 12:39 -- END OF BLOCK -- Alan Cox
2003-07-14 12:50 ` Marcelo Tosatti
2003-07-14 12:56 ` Alan Cox
2003-07-14 13:03 ` Marcelo Tosatti
2003-07-14 17:41 ` Jan Kara
2003-07-14 18:42 ` Alan Cox [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=1058208131.561.100.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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).