From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Alex Zarochentsev <zam@namesys.com>
Cc: Gianni Tedesco <gianni@scaramanga.co.uk>,
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: new reiser4 snapshot is available
Date: Fri, 14 Nov 2003 14:27:29 +0100 [thread overview]
Message-ID: <3FB4D841.5000700@gmx.net> (raw)
In-Reply-To: <20031114131637.GK1278@backtop.namesys.com>
Alex Zarochentsev wrote:
> I made a cleanup for reiser4 patches (by removing UML-specific changes),
> you can see result here:
>
> http://namesys.com/snapshots/2003.11.17/cleaned-up/
That directory doesn't exist.
Carl-Daniel
next prev parent reply other threads:[~2003-11-14 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 14:34 new reiser4 snapshot is available Alex Zarochentsev
2003-11-14 9:42 ` Alex Zarochentsev
2003-11-14 11:04 ` Gianni Tedesco
2003-11-14 11:20 ` Alex Zarochentsev
2003-11-14 13:16 ` Alex Zarochentsev
2003-11-14 13:27 ` Carl-Daniel Hailfinger [this message]
2003-11-14 13:32 ` Alex Zarochentsev
-- strict thread matches above, loose matches on Subject: below --
2003-11-14 10:43 Svetoslav Slavtchev
2003-11-14 11:22 Svetoslav Slavtchev
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=3FB4D841.5000700@gmx.net \
--to=c-d.hailfinger.kernel.2003@gmx.net \
--cc=gianni@scaramanga.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=zam@namesys.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.