From: Eli Zaretskii <eliz@gnu.org>
To: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] catch syscall -- try 3 -- Introduction
Date: Tue, 18 Nov 2008 22:56:00 -0000 [thread overview]
Message-ID: <utza4lsh3.fsf@gnu.org> (raw)
In-Reply-To: <1226987110.5454.31.camel@miki>
> From: =?ISO-8859-1?Q?S=E9rgio?= Durigan =?ISO-8859-1?Q?J=FAnior?= <sergiodj@linux.vnet.ibm.com>
> Date: Tue, 18 Nov 2008 03:45:10 -0200
>
> ... and other minor changes. Unfortunately (only for Eli, apparently), I
> decided to keep the mechanism the way it is, so you'll still find
> syscalls being stored as numbers in this version of the patch. That's
> not personal; I only thought that people in general were happy with the
> way I did.
That's okay, I'm used to have my opinions overruled here.
next prev parent reply other threads:[~2008-11-18 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 19:56 Sérgio Durigan Júnior
2008-11-18 22:56 ` Eli Zaretskii [this message]
2008-11-25 16:54 ` Sérgio Durigan Júnior
2008-12-09 19:36 ` Sérgio Durigan Júnior
2008-12-22 20:29 ` Sérgio Durigan Júnior
2009-01-16 2:26 ` teawater
2009-01-16 14:56 ` Daniel Jacobowitz
2009-01-16 16:23 ` Sérgio Durigan Júnior
2009-01-17 14:05 ` teawater
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=utza4lsh3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@linux.vnet.ibm.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