From: Andi Drebes <lists-receive@programmierforen.de>
To: Diego Calleja <diegocg@gmail.com>
Cc: linux-btrfs@vger.kernel.org, Andi Kleen <andi@firstfloor.org>
Subject: Re: Proper error handling on NULL pointers
Date: Thu, 22 Oct 2009 18:23:28 +0200 [thread overview]
Message-ID: <200910221823.29267.lists-receive@programmierforen.de> (raw)
In-Reply-To: <200910221610.29088.diegocg@gmail.com>
> > I'd really appreciate to see a TODO section somewhere in the wiki. [..]
>
> There's one (needs updating):
> http://btrfs.wiki.kernel.org/index.php/Development_timeline
> Also, http://btrfs.wiki.kernel.org/index.php/Project_ideas has some ideas.
Yes, I've already seen them. They are quite feature-/highlevel-oriented. I thought of something more detailed focusing on cleanups / errors / etc.
Cheers,
Andi
next prev parent reply other threads:[~2009-10-22 16:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 10:36 Proper error handling on NULL pointers Andi Drebes
2009-10-21 17:43 ` Diego Calleja
2009-10-22 10:15 ` Andi Drebes
2009-10-22 14:10 ` Diego Calleja
2009-10-22 16:23 ` Andi Drebes [this message]
2009-10-23 18:08 ` Jeff Mahoney
2009-10-26 9:14 ` Chris Mason
2009-10-26 14:24 ` Jeff Mahoney
2009-10-30 13:27 ` Jeff Mahoney
2009-10-30 13:49 ` Chris Mason
2009-10-26 9:23 ` Chris Mason
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=200910221823.29267.lists-receive@programmierforen.de \
--to=lists-receive@programmierforen.de \
--cc=andi@firstfloor.org \
--cc=diegocg@gmail.com \
--cc=linux-btrfs@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.