Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Muhammad Bilal <mbilal@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH PR gdb/15715] 'set history filename' to by immediately converted to absolute path.
Date: Tue, 30 Jul 2013 10:09:00 -0000	[thread overview]
Message-ID: <51F790BE.9020306@redhat.com> (raw)
In-Reply-To: <51F78DB7.8010902@codesourcery.com>

On 07/30/2013 10:56 AM, Muhammad Bilal wrote:
> On 07/29/2013 07:20 PM, Pedro Alves wrote:

>>> >>   static void
>>> >> +set_history_filename (char *args, int from_tty, struct cmd_list_element *c)
>>> >> +{
>>> >> +  /*We include the current directory so that if the user changes
>>> >> +    directories the file written will be the same as the one
>>> >> +    that was read.  */
>> > Formatting still not right.  Add a space after '/*', and then reindent.
>> > Also, there's trailing whitespace in the first two lines that should not
>> > The correct format is:
>> >
>> >     /* We include the current directory so that if the user changes
>> >        directories the file written will be the same as the one that
>> >        was read.  */

...

> 2013-07-30  Muhammad Bilal  <mbilal@codesorcery.com>
> 
>          PR gdb/15715
>          * top.c: include "filenames.h"

My initial suggestion was:

          * top.c: Include "filenames.h".

That is, uppercase "include", and finish sentence with period.
Please fix this.

>  static void
> +set_history_filename (char *args, int from_tty, struct cmd_list_element *c)
> +{
> +  /* We include the current directory so that if the user changes    
> +     directories the file written will be the same as the one 
> +     that was read. */

The trailing whitespace in first two comment lines is still there.  And
this lost the double space after period; please add it back.  Or just
copy the right formatting I pasted in the previous email...

-- 
Pedro Alves


  reply	other threads:[~2013-07-30 10:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <97B73E257CC18646B0B5D3DD77DCBDD15DA063@EU-MBX-02.mgc.mentorg.com>
2013-07-12 11:05 ` Bilal, Muhammad
2013-07-19 10:22   ` Muhammad Bilal
2013-07-26  5:13     ` Muhammad Bilal
2013-07-26 12:49   ` Pedro Alves
2013-07-29  6:12     ` Muhammad Bilal
2013-07-29 14:43       ` Pedro Alves
2013-07-30  9:56         ` Muhammad Bilal
2013-07-30 10:09           ` Pedro Alves [this message]
2013-07-30 10:47             ` Muhammad Bilal
2013-07-30 11:33               ` Pedro Alves
2013-07-30 12:11                 ` Muhammad Bilal

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=51F790BE.9020306@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mbilal@codesourcery.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