From: Andrew Morton <akpm@osdl.org>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: chris@sigsegv.plus.com, linux-kernel@vger.kernel.org,
ext2-devel@lists.sourceforge.net
Subject: Re: Hang during rm on ext2 mounted sync (2.6.14-rc2+)
Date: Fri, 23 Sep 2005 12:47:27 -0700 [thread overview]
Message-ID: <20050923124727.7c3ffa22.akpm@osdl.org> (raw)
In-Reply-To: <9a8748490509231245d26d875@mail.gmail.com>
Jesper Juhl <jesper.juhl@gmail.com> wrote:
>
> On 9/23/05, Andrew Morton <akpm@osdl.org> wrote:
> [snip]
> >
> > We ought to have the git bisection process documented in the kernel tree,
> > but we don't, alas. There's stuff at http://lkml.org/lkml/2005/6/24/234
> > but a standalone document which walks people through installing git,
> > pulling the initial tree, building and bisecting is needed (hint).
> >
>
> If noone else is doing this then I'll write such a document.
Thanks.
> If someone has already started writing it, then please let me know so
> we don't duplicate work. I'll get write it during the weekend if I
> hear nothing.
I suspect you're pretty safe ;)
next prev parent reply other threads:[~2005-09-23 19:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 16:37 Hang during rm on ext2 mounted sync (2.6.14-rc2+) Chris Sykes
2005-09-22 20:49 ` Chris Sykes
2005-09-23 8:57 ` Andrew Morton
2005-09-23 12:19 ` Chris Sykes
2005-09-23 13:22 ` Chris Sykes
2005-09-23 19:18 ` Andrew Morton
2005-09-23 19:45 ` Jesper Juhl
2005-09-23 19:47 ` Andrew Morton [this message]
2005-09-23 20:11 ` Alexey Dobriyan
2005-09-23 20:06 ` Jesper Juhl
2005-09-23 20:23 ` Andrew Morton
2005-09-23 20:51 ` Jesper Juhl
2005-09-24 12:14 ` Chris Sykes
2005-09-24 14:28 ` Chris Sykes
2005-09-24 15:47 ` [PATCH]: Fix ext2_new_inode() failure paths Chris Sykes
2005-09-24 17:33 ` [PATCH]: Fix ext3_new_inode() " Chris Sykes
2005-09-24 17:39 ` Hang during rm on ext2 mounted sync (2.6.14-rc2+) Andrew Morton
2005-09-25 10:56 ` Chris Sykes
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=20050923124727.7c3ffa22.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=chris@sigsegv.plus.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@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