public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Kirk True <kirk@mustardgrain.com>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Failures in e2fsprogs-1.39-tyt3 'make check'
Date: Mon, 4 Jun 2007 08:38:51 -0700 (PDT)	[thread overview]
Message-ID: <114319.28763.qm@web611.biz.mail.mud.yahoo.com> (raw)
In-Reply-To: <20070604125109.GA20342@thunk.org>

Hi Theodore,

> > Sorry if this is a documented, known issue. I'm just being paranoid
> and
> > don't want to do a 'make install' if it will hose up the box.
> 
> Yes, it's known.  Note that e2fsprogs 1.39-tyt3 is really only meant
> for ext4 developers.  If you're not trying to use ext4 (and it's
> really not meant for production use yet), you should be using
> e2fsprogs.1.39 or e2fsprogs WIP-20070407.

Thanks for the quick reply.

Yes - I'm trying to get into ext4 development, so I'll assume these
aren't fatal and proceed.

Thanks!
Kirk

      reply	other threads:[~2007-06-04 15:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-04  8:18 Failures in e2fsprogs-1.39-tyt3 'make check' Kirk True
2007-06-04 12:51 ` Theodore Tso
2007-06-04 15:38   ` Kirk True [this message]

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=114319.28763.qm@web611.biz.mail.mud.yahoo.com \
    --to=kirk@mustardgrain.com \
    --cc=linux-ext4@vger.kernel.org \
    --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