Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: gdb-patches ml <gdb-patches@sourceware.org>,
	 	Christopher Faylor
	<cgf-use-the-mailinglist-please@sourceware.org>
Subject: Re: [Prec/RFA] fix build error of prec in cygwin
Date: Thu, 21 May 2009 16:43:00 -0000	[thread overview]
Message-ID: <daef60380905210943n5e089918n2a4b7ade1f917a74@mail.gmail.com> (raw)
In-Reply-To: <20090521152621.GA27524@ednor.casa.cgf.cx>

Hi Christopher,

On Thu, May 21, 2009 at 23:26, Christopher Faylor
<cgf-use-the-mailinglist-please@sourceware.org> wrote:
> On Thu, May 21, 2009 at 10:38:58AM +0800, Hui Zhu wrote:
>>Ping
>
> You are aware that it took you about seven days to respond to one of my
> messages right?
>

Sorry for that. To get a cygwin environment is very hard thing for a
linux guy.  And I found that cygwin cannot work with wine.

> I was confused by the fact that you didn't seem to be using CVS to
> generate your diffs and, on closer inspection, I see that there are
> multiple places where coercion is used inappropriately when the format
> specifier should just have matched the parameter.

Sorry for my poor english.  I got patch with quilt.

>
> Some of your changes are now using "%u" with "(int) sizeof" (which is
> wrong) and some of the existing code is just using "(int) sizeof" with
> "%d" which is also wrong.
>
> So, in other words, the file was already not quite "right" and I don't
> think your changes are getting it much closer to "right".
>

Thanks for you help me review my patch.  Could you give me some help with it?
Actually, try something with cygwin still a very hard thing for me.  I
just can use it in a notebook of other guy.  And I had return it.
Maybe you can make a patch for this bug.  That will be very great for me.

> I was not implying that your changes didn't fix compiler errors.  I was
> saying that I didn't think they were the correct way to fix the errors.
> However, since I am apparently the only person who cares about this
> stuff, and it doesn't seem like my point is getting across, I think I'll
> just shut up now.  Other, global maintainers have said that they were ok
> with your changes so I'm not going to object even if they don't make
> sense to me.

Please do not misunderstand us.  I just get a mail from Pierre who
report this bug.  And this mail just say this patch test with cygwin
is OK.  Because I let Pierre help me test the patch with cygwin.  That
is all.


Thanks,
Hui


  parent reply	other threads:[~2009-05-21 16:43 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-10 17:31 Hui Zhu
2009-05-10 17:48 ` Christopher Faylor
2009-05-10 18:07   ` Hui Zhu
2009-05-10 23:51     ` Christopher Faylor
2009-05-18  8:43       ` Hui Zhu
2009-05-18 15:35         ` Christopher Faylor
2009-05-19  2:34           ` Hui Zhu
2009-05-21  2:39             ` Hui Zhu
2009-05-21 15:26               ` Christopher Faylor
2009-05-21 15:35                 ` Pedro Alves
2009-05-21 17:35                   ` Christopher Faylor
2009-05-21 16:43                 ` Hui Zhu [this message]
2009-05-21 17:38                   ` Christopher Faylor
2009-05-21 23:14                     ` Hui Zhu
2009-05-22  0:46                       ` Christopher Faylor
2009-05-22  2:12                         ` Hui Zhu
2009-05-22  4:13                           ` Christopher Faylor
2009-05-22  5:53                             ` Hui Zhu
2009-05-22  6:05                             ` Joel Brobecker
2009-05-22  6:56                               ` Eli Zaretskii
2009-05-22  8:42                                 ` Hui Zhu
2009-05-22  9:37                                   ` Eli Zaretskii
2009-05-22 10:11                                   ` Jie Zhang
2009-05-22  9:06                                 ` Hui Zhu
2009-05-22  9:30                                   ` Eli Zaretskii
2009-05-22 14:11                                     ` Hui Zhu
2009-05-22 17:02                               ` Christopher Faylor

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=daef60380905210943n5e089918n2a4b7ade1f917a74@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox