From: Ted Ts'o <tytso@mit.edu>
To: Lukas Czerner <lczerner@redhat.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] resize2fs: handle exactly-16T filesystems in resize2fs
Date: Thu, 16 Dec 2010 19:15:57 -0500 [thread overview]
Message-ID: <20101217001557.GE4455@thunk.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1012160957320.2781@dhcp-lab-213.englab.brq.redhat.com>
On Thu, Dec 16, 2010 at 10:00:26AM +0100, Lukas Czerner wrote:
>
> which version of e2fsprogs are you referring to ? When I look at master
> branch I can see than those changes are already in there. Except the check
> if the new size is too large. Am I missing something ?
The 1.41.x series is on the "maint" branch.
The 1.42 version is on the main "master" and "next" branch, where
"next" is where I'll check in things initially, and then "master"
catches up with "next". I took this from git, with the basic idea
being that if there are people who are testing next, and people who
are using the "master", hopefully problems get noticed and fixed
before people are using "master" grab a commit. To be honest there
probably aren't enough people tracking next and master for this to
make a huge amount of difference, but I'm following this scheme
anyway.
- Ted
next prev parent reply other threads:[~2010-12-17 0:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 4:37 [PATCH] resize2fs: handle exactly-16T filesystems in resize2fs Eric Sandeen
2010-12-16 9:00 ` Lukas Czerner
2010-12-16 14:57 ` Eric Sandeen
2010-12-17 0:15 ` Ted Ts'o [this message]
2010-12-17 8:06 ` Stephan Boettcher
2010-12-17 0:18 ` Ted Ts'o
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=20101217001557.GE4455@thunk.org \
--to=tytso@mit.edu \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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.