From: Jeff Mahoney <jeffm@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: [PATCH 03/05] reiserfs: rework reiserfs_warning
Date: Fri, 16 Jun 2006 15:33:46 -0400 [thread overview]
Message-ID: <4493079A.2080004@suse.com> (raw)
In-Reply-To: <449301D3.3070303@namesys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hans Reiser wrote:
> Jeffrey Mahoney wrote:
>
>> Hans Reiser wrote:
>>
>>> 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.
>>
>> I can interpolate which ones are Chris's since I generally see them
>> before they get submitted upstream. For the other ones, I'd rather
>> have people speak up and claim them.
>
> How about creating a list of them that are not Chris's or yours, and
> then we send them to whichever person still around wrote most of that
> file to claim or deny?
Sure. I claimed most of mine when I made the patch. I can make the ones
in journal.c use clm-. Generating a list for the rest would be easiest
by grepping the third patch in the series for "reiserfs-" since there is
no unique identifier now to easily point out which message needs help.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFEkweaLPWxlyuTD7IRAvp2AJ9gqIo+yLw4/OKYc4tyOmfTaLSPPwCgiUPT
bQANpWPq89+tP4HIOGiJlo0=
=LlYD
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-06-16 19:33 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
2006-06-16 5:22 ` Jeffrey Mahoney
2006-06-16 19:09 ` Hans Reiser
2006-06-16 19:33 ` Jeff Mahoney [this message]
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=4493079A.2080004@suse.com \
--to=jeffm@suse.com \
--cc=reiser@namesys.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.