From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Christian Kujau <lists@nerdbynature.de>, linux-ext4@vger.kernel.org
Subject: Re: e2fsprogs-interim scm tree?
Date: Tue, 20 Nov 2007 13:45:22 -0500 [thread overview]
Message-ID: <20071120184522.GF13125@thunk.org> (raw)
In-Reply-To: <4742F5A9.3070301@redhat.com>
On Tue, Nov 20, 2007 at 08:56:41AM -0600, Eric Sandeen wrote:
> Theodore Tso wrote:
> > On Tue, Nov 20, 2007 at 11:24:03AM +0100, Christian Kujau wrote:
> >>> Note that the userspace code still needs a lot of work.
> >>> It's for this reason that I haven't been recommending people use it for
> >>> production systems just yet.
> >> Understood. But the more ppl testing your stuff the better, right?
> >
> > Oh, absolutely. I just don't think it's fair to encourage people to
> > use something that might cause them to risk their data unless they are
> > going into it with their eyes wide open.
>
> Please do report any problems you find, though. Ted has said that the
> sourceforge bugtracker is the right place to do this for now.
BTW, when reporting a bugs against the git tree, please include the
branch and the git ID (i.e., that which is reported by git-describe),
so there is no question which version you were running at the time.
The git ID won't be helpful if you have your own local commits against
the tree, but it can be useful if you are reporting a bug against the
"pu" branch and it has since been rewound as patches get rebased and
revised.
- Ted
next prev parent reply other threads:[~2007-11-20 18:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 0:42 e2fsprogs-interim scm tree? Christian Kujau
2007-11-20 3:11 ` Theodore Tso
2007-11-20 10:24 ` Christian Kujau
2007-11-20 14:04 ` Theodore Tso
2007-11-20 14:56 ` Eric Sandeen
2007-11-20 18:45 ` Theodore Tso [this message]
2007-11-20 19:21 ` Christian Kujau
2007-11-21 13:17 ` Thierry Vignaud
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=20071120184522.GF13125@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=lists@nerdbynature.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox