From: Doug Evans <dje@google.com>
To: asmwarrior <asmwarrior@gmail.com>
Cc: gdb-patches@sourceware.org, Chris Sutcliffe <ir0nh34d@gmail.com>
Subject: Re: [windows] patch to set breakpoint in a dll
Date: Fri, 16 Mar 2012 22:23:00 -0000 [thread overview]
Message-ID: <CADPb22RSiohR5hbQyhRsORk0zzBEL3bX5-GVWJjJA45nuHuegw@mail.gmail.com> (raw)
In-Reply-To: <4F629CE5.8030301@gmail.com>
On Thu, Mar 15, 2012 at 6:52 PM, asmwarrior <asmwarrior@gmail.com> wrote:
> Ok, this is the new patch.(I have problem using the TortoiseGit to generate
> a diff between two revisions.you can see, the file name is long and dirty)
>
>
> Also, the log message is what you wrote:
>
>
> 2012-03-14 Zhang Yuanhui <asmwarrior@gmail.com>
>
> * source.c (find_and_open_source): Consistently pass resulting
> full path through xfullpath.
>
>
> My family name is "Zhang", so I'm not sure it should be put before the given
> name or after the given name. The Chinese name and English name have
> different formats.
I say it's your choice. I just copied from an existing example in ChangeLog.
Heh. One last nit. Blank line between these two lines.
+ char *lpath;
+ lpath = xfullpath (*fullname);
[or combine them, but then you still need a blank line afterwards]
Can you check the patch in? I'm happy to for you if necessary (at
which point I can just insert the blank line before checkin).
next prev parent reply other threads:[~2012-03-16 22:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 15:10 asmwarrior
2012-03-07 18:46 ` Doug Evans
2012-03-08 2:18 ` asmwarrior
2012-03-08 22:39 ` Doug Evans
2012-03-10 4:39 ` asmwarrior
2012-03-14 18:26 ` Doug Evans
2012-03-16 1:52 ` asmwarrior
2012-03-16 22:23 ` Doug Evans [this message]
2012-03-17 1:13 ` asmwarrior
2012-04-11 15:25 ` asmwarrior
2012-04-11 18:43 ` Doug Evans
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=CADPb22RSiohR5hbQyhRsORk0zzBEL3bX5-GVWJjJA45nuHuegw@mail.gmail.com \
--to=dje@google.com \
--cc=asmwarrior@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=ir0nh34d@gmail.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