All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: adobriyan@gmail.com, 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 22:51:16 +0200	[thread overview]
Message-ID: <9a87484905092313513bdd16d3@mail.gmail.com> (raw)
In-Reply-To: <20050923132308.7660e873.akpm@osdl.org>

On 9/23/05, Andrew Morton <akpm@osdl.org> wrote:
> Jesper Juhl <jesper.juhl@gmail.com> wrote:
> >
> > On 9/23/05, Alexey Dobriyan <adobriyan@gmail.com> wrote:
> > > On Fri, Sep 23, 2005 at 09:45:37PM +0200, Jesper Juhl wrote:
> > > > On 9/23/05, Andrew Morton <akpm@osdl.org> wrote:
> > > > > 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.
> > > > 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.
> > >
> > > Bisecting itself is described at Documentation/git-bisect.txt:
> > >
> > > http://kernel.org/git/?p=git/git.git;a=blob;h=b124b0751c195db82a49d0bcf434da429ec71019;hb=7fe2fc79358673a909d71e62d3f80ffe0f525fce;f=Documentation/git-bisect.txt
> > >
> >
> > Thanks, had not seen that document.
> >
> > So, should I just add to that a section on how to get and install git
> > and pull the tree, or put that in a new document and just refer to
> > that document at the top of git-bisect.txt ?
> > Any preferences?
>
> A new document, I think.  People seem to go nuts over this sort of thing
> and write a whole encyclopedia.  I think we'd be better off with just a
> recipe:
>
[snip]
>
> The shorter the better, with exact example commands.
>

Understood. Will do.


--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2005-09-23 20:51 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
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 [this message]
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=9a87484905092313513bdd16d3@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=chris@sigsegv.plus.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.