From: Hans Reiser <reiser@namesys.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: [PATCH 03/05] reiserfs: rework reiserfs_warning
Date: Thu, 15 Jun 2006 22:04:35 -0700 [thread overview]
Message-ID: <44923BE3.7040303@namesys.com> (raw)
In-Reply-To: <20060616041900.GA5395@locomotive.unixthugs.org>
Please instead compile a list of warnings and errors that lack names of
programmers responsible for that line of code, and ask Chris Mason which
of them are his.
next prev parent reply other threads:[~2006-06-16 5:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 4:19 [PATCH 03/05] reiserfs: rework reiserfs_warning Jeff Mahoney
2006-06-16 5:04 ` Hans Reiser [this message]
2006-06-16 5:22 ` Jeffrey Mahoney
2006-06-16 19:09 ` Hans Reiser
2006-06-16 19:33 ` Jeff Mahoney
2006-06-16 19:09 ` Hans Reiser
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=44923BE3.7040303@namesys.com \
--to=reiser@namesys.com \
--cc=jeffm@suse.com \
--cc=reiserfs-list@namesys.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 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.