Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: New format of 7.6 branch gdb/ChangeLog?
Date: Thu, 25 Apr 2013 08:07:00 -0000	[thread overview]
Message-ID: <CANFwon2N3nVxhGFh4YTf8jVvSfp-Sq_uftx2+tqTFbvr4Kd2tA@mail.gmail.com> (raw)
In-Reply-To: <20130425074044.GE3458@adacore.com>

On Thu, Apr 25, 2013 at 3:40 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>> It shoud like this?
>
> I am referring you to the GNU Coding Standard manual:
> http://www.gnu.org/prep/standards/standards.html#Change-Logs
>
>
>> gdb/
>> 2013-04-24  Hui Zhu  <hui@codesourcery.com>
>>
>>         PR gdb/15165
>>
>>         * breakpoint.c (dprintf_print_recreate): New.
>>         (save_breakpoints): Let it not save dprintf commands.
>>         (initialize_breakpoint_ops): Set dprintf_print_recreate.
>>
>> 2013-04-19  Vladimir Kargov <kargov@gmail.com>
>>             Pedro Alves  <palves@redhat.com>
>>
>>         * i387-tdep.c (i387_print_float_info): Use gdb_byte for pointer to
>>         value contents.
>
> You put the "gdb/" back again. The correct answer is:
>
> 2013-04-24  Hui Zhu  <hui@codesourcery.com>
>
>         PR gdb/15165
>         * breakpoint.c (dprintf_print_recreate): New.
>         (save_breakpoints): Let it not save dprintf commands.
>         (initialize_breakpoint_ops): Set dprintf_print_recreate.
>
> 2013-04-19  Vladimir Kargov <kargov@gmail.com>
>             Pedro Alves  <palves@redhat.com>
>
>         * i387-tdep.c (i387_print_float_info): Use gdb_byte for pointer to
>         value contents.
>
> I removed the "gdb/" (which, if you think about it, provides no extra
> information), and also removed the empty line after "PR gdb/...".
>
> You probably got confused because people use the "gdb/" in their
> email to specify which ChangeLog the entry is belonging to.

I see.  Thanks for your help.
I fixed them all in
http://www.sourceware.org/ml/gdb-cvs/2013-04/msg00235.html
http://www.sourceware.org/ml/gdb-cvs/2013-04/msg00236.html

Best,
Hui

>
> --
> Joel


  reply	other threads:[~2013-04-25  8:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANFwon0v3pwvC_iJbEnzVp4ZB-B+zphAg-C+hrQqF153P+M_ag@mail.gmail.com>
2013-04-25  6:48 ` Joel Brobecker
2013-04-25  7:17   ` Hui Zhu
2013-04-25  7:25     ` Joel Brobecker
2013-04-25  7:29       ` Hui Zhu
2013-04-25  7:40         ` Joel Brobecker
2013-04-25  8:07           ` Hui Zhu [this message]
2013-04-26 10:54           ` Pedro Alves

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=CANFwon2N3nVxhGFh4YTf8jVvSfp-Sq_uftx2+tqTFbvr4Kd2tA@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@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