From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: fche@redhat.com
Cc: hans-peter.nilsson@axis.com, gdb-patches@sources.redhat.com
Subject: Re: sim/cris maintainership and patch ping: pipe support and minor endian cleanup.
Date: Wed, 05 Jan 2005 03:00:00 -0000 [thread overview]
Message-ID: <200501050300.j0530LsC023640@ignucius.se.axis.com> (raw)
In-Reply-To: <y0mhdlw28ow.fsf@toenail.toronto.redhat.com> (fche@redhat.com)
> From: fche@redhat.com (Frank Ch. Eigler)
> Date: 04 Jan 2005 16:19:59 -0500
> HP wrote:
> > [RFA:] Minor sim callback endian cleanup.
> > <URL:http://sources.redhat.com/ml/gdb-patches/2004-12/msg00324.html>
> > sim/common: pipe syscall support
> > <URL:http://sources.redhat.com/ml/gdb-patches/2004-12/msg00378.html>
> > Ok to commit them?
> I rather think that someone touching that code as frequently
> as you do
No, no, I just broke up one large patch in time and space!
(And oh, revisited some issues in it, improving portability. :-)
> should automagically get recognized as a maintainer for said code; in
> this case sim/common.
Muhahahahaa!^W I mean, I'd be honored.
brgds, H-P
prev parent reply other threads:[~2005-01-05 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 15:30 Hans-Peter Nilsson
2005-01-04 21:20 ` Frank Ch. Eigler
2005-01-05 3:00 ` Hans-Peter Nilsson [this message]
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=200501050300.j0530LsC023640@ignucius.se.axis.com \
--to=hans-peter.nilsson@axis.com \
--cc=fche@redhat.com \
--cc=gdb-patches@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox