From: Mark Trumpold <markt-qk0wvQ0ghJwAvxtiuMwx3w@public.gmane.org>
To: "linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Obtaining kernel patches
Date: Thu, 05 Sep 2013 07:54:22 -0700 [thread overview]
Message-ID: <CE4DE92E.8DF9%markt@netqa.com> (raw)
Hello nilfs'ers:
I've been actively using nilfs in my project for a couple years now,
and follow closely the development via this mailing list.
In my environment nilfs has been very stable; however, the way I'm
using it does not stress any existing race conditions (fairly quiet
activity).
Recently however I have a case where a snapshot disappeared, and a
message in the syslog from the nilfs cleaner "..snapshot count mismatch..".
I'm using Debian and the 3.3.1 kernel, and am wondering how to best obtain
all important patches to date.
Thanks and best regards,
Mark Trumpold
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2013-09-05 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 14:54 Mark Trumpold [this message]
[not found] ` <CE4DE92E.8DF9%markt-qk0wvQ0ghJwAvxtiuMwx3w@public.gmane.org>
2013-09-06 6:36 ` Obtaining kernel patches Vyacheslav Dubeyko
2013-09-06 14:33 ` Mark Trumpold
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=CE4DE92E.8DF9%markt@netqa.com \
--to=markt-qk0wvq0ghjwavxtiumwx3w@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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