All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ookhoi <ookhoi@humilis.net>
To: Ookhoi <ookhoi@humilis.net>
Cc: Nikita Danilov <Nikita@namesys.com>,
	Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>,
	Reiserfs mail-list <Reiserfs-List@namesys.com>
Subject: Re: [ANNOUNCE]: reiser4 snapshot
Date: Fri, 17 Jan 2003 13:11:34 +0100	[thread overview]
Message-ID: <20030117131134.B8821@humilis> (raw)
In-Reply-To: <20030117130916.A8821@humilis>

Ookhoi wrote (ao):
# Nikita Danilov wrote (ao):
# > new reiser4 snapshot is available at:
# > 
# > http://www.namesys.com/snapshots/2003.01.16/
# 
# Thanks :-)
# 
# > It is released as a patch against linux-2.5.58 kernel. It should also
# > work with current (January 16th) bk snapshot at
# > http://linux.bkbits.net/linux-2.5
# > 
# > This is mostly bug fixing release.
# > 
# > READ.ME file contains changelog.
# 
# Can you please have a look at the READ.ME? It contains old info from the
# former snapshot.

Ugh! Never mind .. I did a wget, but had the (old) file already. It was
named READ.ME.1 due to that, and of course I only noticed this 1ms
_after_ I kicked away the message ..

  reply	other threads:[~2003-01-17 12:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-17 10:33 [ANNOUNCE]: reiser4 snapshot Nikita Danilov
2003-01-17 12:09 ` Ookhoi
2003-01-17 12:11   ` Ookhoi [this message]
2003-01-17 12:12   ` [reiserfs-dev] " Oleg Drokin
2003-01-17 12:14     ` Ookhoi
  -- strict thread matches above, loose matches on Subject: below --
2003-02-13 14:44 Nikita Danilov
2003-02-13 19:32 ` Ookhoi
2003-02-14  6:53   ` Oleg Drokin
2002-12-24 16:40 Nikita Danilov
2003-01-16  8:14 ` Ookhoi
2002-11-20 10:30 Nikita Danilov
2002-11-12 15:42 Nikita Danilov
2002-11-12 15:48 ` Nikita Danilov
2002-11-13  8:14 ` Todd Lyons

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=20030117131134.B8821@humilis \
    --to=ookhoi@humilis.net \
    --cc=Nikita@namesys.com \
    --cc=Reiserfs-Dev@namesys.com \
    --cc=Reiserfs-List@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.