From: Fabio Olive Leite <fleite@redhat.com>
To: nfs@lists.sourceforge.net
Subject: Re: osync-on-error getting upstream?
Date: Fri, 16 Nov 2007 16:11:56 -0200 [thread overview]
Message-ID: <20071116181156.GB3864@sleipnir.redhat.com> (raw)
In-Reply-To: <1195233908.7653.64.camel@heimdal.trondhjem.org>
On Fri, Nov 16, 2007 at 12:25:08PM -0500, Trond Myklebust wrote:
>
> I'd say, roughly, a couple of weeks ago... :-)
:-D I must've been checking the wrong tree... hehehe :)
Thanks!
Fabio
--
ex sed lex awk yacc, e pluribus unix, amem
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
prev parent reply other threads:[~2007-11-16 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 17:13 osync-on-error getting upstream? Fabio Olive Leite
2007-11-16 17:25 ` Trond Myklebust
2007-11-16 18:11 ` Fabio Olive Leite [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=20071116181156.GB3864@sleipnir.redhat.com \
--to=fleite@redhat.com \
--cc=nfs@lists.sourceforge.net \
/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