linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: Girish Shilamkar <Girish.Shilamkar@sun.com>
Cc: Ext4 <linux-ext4@vger.kernel.org>, adilger@sun.com
Subject: Re: e2fsprogs segfaults during make check
Date: Mon, 8 Feb 2010 09:28:49 -0500	[thread overview]
Message-ID: <20100208142849.GJ4494@thunk.org> (raw)
In-Reply-To: <1265638817.3882.31.camel@metis>

On Mon, Feb 08, 2010 at 07:50:17PM +0530, Girish Shilamkar wrote:
> > #3) Try downloading:
> > 
> >     http://master.kernel.org/~tytso/e2fsprogs_1.41.10-rc1.tar.gz
> > 
> > ... and see if you can see the problem there.

> The problem is not seen for this version. 

OK, so I'll treat this as "fixed in 1.41.10".

> Any tentative dates for 1.41.10 release ?

I'm working on the release notes right now.  :-)

    	       	   	   	       - Ted

  reply	other threads:[~2010-02-08 14:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08  7:31 e2fsprogs segfaults during make check Girish Shilamkar
2010-02-08 12:16 ` tytso
2010-02-08 14:20   ` Girish Shilamkar
2010-02-08 14:28     ` tytso [this message]
2010-02-08 15:57   ` 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=20100208142849.GJ4494@thunk.org \
    --to=tytso@mit.edu \
    --cc=Girish.Shilamkar@sun.com \
    --cc=adilger@sun.com \
    --cc=linux-ext4@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).