From: "Edward Shishkin" <edward.shishkin@gmail.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>,
Vladimir Saveliev <Vladimir.Saveliev@sun.com>
Subject: Re: [PATCH 2/2] reiserfs: Add mount counting
Date: Tue, 4 Dec 2007 01:56:33 +0300 [thread overview]
Message-ID: <5c7c368b0712031456p120634behc13f2d546df8659b@mail.gmail.com> (raw)
In-Reply-To: <475475E5.1010400@suse.com>
On 12/4/07, Jeff Mahoney <jeffm@suse.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Edward Shishkin wrote:
> > On 12/3/07, Jeff Mahoney <jeffm@suse.com> wrote:
> > Edward Shishkin wrote:
> >>>> Hi Jeff.
> >>>>
> >>>> Personally, I don't object.
> >>>> What does official reservation mean?
> >>>> I can send a request to Hans, but I guess
> >>>> we'll receive his "yes" or "no" with substantial delay..
> > I just mean that those 12 bytes in the superblock are guaranteed not to
> > be used for something else. Given the pace of reiserfs development, I
> > don't expect this to be a problem as there are 76 more of them. :)
> >
> >> Well, I promise to not use them for something else ;)
>
> Great. That's the assurance I was looking for. :)
>
> >> It seems we need something like reiserfsprogs-3.6.20?
>
> I actually posted a patch against reiserfsprogs-3.6.20 that reserves the
> same fields. It also implements the use of those fields. I have an
> updated version that treats timestamps in the future as suspect and
> forces a check. I'll post the update later today.
Sorry, I am a bit confused..
The latest git version of reiserfsprogs is 3.6.19;
The latest website version is also 3.6.19.
At the same time I can google and see that some distros
use reiserfsprogs-3.6.20.
Suse 10.3 uses "reiserfs utility package" 3.6.19-92
Also I remember that Vladimir worked on some version
of reiserfsprogs not so long ago.
Any ideas about really latest version?
Thanks,
Edward.
>
> If there's interest in releasing a reiserfsprogs 3.6.21, I have some
> patches that we've maintaining locally for a while I'd like to submit
> for inclusion. Also, I don't think the code base would hurt from a
> whitespace removal run. :)
>
> - -Jeff
>
> - --
> Jeff Mahoney
> SUSE Labs
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.4-svn0 (GNU/Linux)
> Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
>
> iD8DBQFHVHXkLPWxlyuTD7IRAhM1AJ9vBrHDW3uhRb15HnO6BNpQGOdIiwCfUHyL
> aUwybiy8ZfuOwg0lXZ+xEKE=
> =DpoT
> -----END PGP SIGNATURE-----
>
next prev parent reply other threads:[~2007-12-03 22:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 22:42 [PATCH 2/2] reiserfs: Add mount counting Jeff Mahoney
2007-12-03 19:46 ` Jeff Mahoney
2007-12-03 20:36 ` Edward Shishkin
2007-12-03 20:40 ` Jeff Mahoney
2007-12-03 20:51 ` Edward Shishkin
2007-12-03 21:32 ` Jeff Mahoney
2007-12-03 22:56 ` Edward Shishkin [this message]
2007-12-03 23:00 ` Jeff Mahoney
2007-12-05 12:22 ` Ric Wheeler
2007-12-05 13:01 ` Vladimir Saveliev
2007-12-05 15:32 ` Jeff Mahoney
2007-12-05 15:39 ` Ric Wheeler
2007-12-05 15:52 ` Jeff Mahoney
2007-12-05 17:53 ` Vladimir Saveliev
2007-12-05 18:18 ` Ric Wheeler
2008-01-24 19:52 ` Jeff Mahoney
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=5c7c368b0712031456p120634behc13f2d546df8659b@mail.gmail.com \
--to=edward.shishkin@gmail.com \
--cc=Vladimir.Saveliev@sun.com \
--cc=jeffm@suse.com \
--cc=reiserfs-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).