linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valerie Aurora <vaurora@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Justin Maggard <jmaggard10@gmail.com>,
	Andreas Dilger <adilger@sun.com>,
	linux-ext4@vger.kernel.org, Nick Dokos <nicholas.dokos@hp.com>,
	Julia Lawall <julia@diku.dk>
Subject: Re: >16TB issues
Date: Wed, 12 Aug 2009 13:59:17 -0400	[thread overview]
Message-ID: <20090812175916.GE11100@shell> (raw)
In-Reply-To: <20090812020439.GE31342@mit.edu>

(Removing Jose from the cc list - his email at IBM is bouncing.)

On Tue, Aug 11, 2009 at 10:04:39PM -0400, Theodore Tso wrote:
> Just to be clear, since it's not clear from me what you said here:
> 
> On Tue, Aug 11, 2009 at 05:39:48PM -0400, Valerie Aurora wrote:
> > By the way, I'm just waiting for Ted's rebase/rewrite of the 64-bit
> > patches to try reproducing and fixing this bug.
> 
> Vs. a few hours later:
> 
> On Tue, Aug 11, 2009 at 09:25:39PM -0400, Valerie Aurora wrote:
> > I am going to stop tracking and fixing 64 bit bugs now.  I stopped
> > actively working on this project in February but wanted to follow up
> > on bugs for a few months.  This is the only outstanding bug report I
> > know of (I'm sure there are more!).
> 
> Are you going to try to reproduce and fix this bug or not?

I didn't realize this wouldn't be clear, but the second email does
override the first.  I won't be trying to reproduce and fix this
particular bug (more likely, set of bugs).

I'm stepping back from tracking bugs in this patch set for a couple of
reasons.  First, I've used all the time allocated for this project for
me by Red Hat.  I am now working on other projects, union mounts at
present, and btrfs utilities next.  Second, you're now the most active
developer on this feature, and the overhead of trying to synchronize
between two developers is far more than the benefit I can contribute.
I feel the project is in good hands now.

I will of course be happy to assist other people working on bugs in
the 64 bit patches, I just won't be taking the lead in tracking and
fixing them.  I'm also happy to answer questions, do code review, help
with spatch scripts, etc. - again, just not taking the lead since I'm
not the lead developer.

-VAL

  reply	other threads:[~2009-08-12 18:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 22:23 >16TB issues Justin Maggard
2009-07-03 14:38 ` Andreas Dilger
2009-07-16 18:04   ` Justin Maggard
2009-07-16 18:59     ` Valerie Aurora
2009-07-21 16:10     ` Andreas Dilger
2009-07-21 18:52       ` Justin Maggard
2009-07-21 18:57         ` Eric Sandeen
2009-07-21 19:21         ` Andreas Dilger
2009-07-22 22:27           ` Justin Maggard
2009-07-27 22:03             ` Valerie Aurora
2009-07-30 22:23             ` Valerie Aurora
2009-08-01  1:24               ` Justin Maggard
2009-08-03 17:20                 ` Valerie Aurora
2009-08-11 21:39                 ` Valerie Aurora
2009-08-11 22:05                   ` Theodore Tso
2009-08-12  1:25                     ` Valerie Aurora
2009-08-12  2:04                       ` Theodore Tso
2009-08-12 17:59                         ` Valerie Aurora [this message]
2009-08-28  2:30                           ` Justin Maggard
2009-08-28 12:40                             ` Theodore Tso
2009-08-28 20:27                               ` Justin Maggard
2009-08-12  4:21 ` Eric Sandeen
2009-08-12  5:35   ` Justin Maggard
2009-08-12 14:12     ` Eric Sandeen

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=20090812175916.GE11100@shell \
    --to=vaurora@redhat.com \
    --cc=adilger@sun.com \
    --cc=jmaggard10@gmail.com \
    --cc=julia@diku.dk \
    --cc=linux-ext4@vger.kernel.org \
    --cc=nicholas.dokos@hp.com \
    --cc=tytso@mit.edu \
    /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).