Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Lukas Durfina <ldurfina@tachyum.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: Updated includes
Date: Sat, 01 Feb 2020 10:15:00 -0000	[thread overview]
Message-ID: <20200201101548.GA19442@adacore.com> (raw)
In-Reply-To: <20200109081731.42472-1-ldurfina@tachyum.com>

Hello,

I had assumed you pushed the patch, but in double-checking,
it does not seem that way. Apologies for the confusion.

The patch is OK to wait, but can you include the ChangeLog entry
in the revision log? It's been pretty traditional in the GDB
project to have the revision log of the commit be the same as
what's sent by email. I'll take this opportunity to make some
suggestions on how to make the revision log a little more useful
to those who use "git log" (I do it a lot myself).  Typically,
it looks like this:

| Fix compilation error with musl in gdb/testsuite/gdb.base/fileio.c
|
| <in most cases, a short description of the problem to better
| understand the circumstances of the change should be provided here>
|
| gdb/ChangeLog:
|
| 	* gdb.base/fileio.c: Remove #include of <sys/errno.h>.
| 	Replace #include of <sys/fcntl.h> by <fcntl.h>.

Thank you!

On Thu, Jan 09, 2020 at 09:17:31AM +0100, Lukas Durfina wrote:
> Fixed compilation with musl.
> ---
>  gdb/testsuite/ChangeLog         | 5 +++++
>  gdb/testsuite/gdb.base/fileio.c | 3 +--
>  2 files changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
> index 3f243641b8..243721f6cb 100644
> --- a/gdb/testsuite/ChangeLog
> +++ b/gdb/testsuite/ChangeLog
> @@ -1,3 +1,8 @@
> +2020-01-09  Lukas Durfina  <ldurfina@tachyum.com>
> +
> +	* gdb.base/fileio.c: Remove #include of <sys/errno.h>.
> +	Replace #include of <sys/fcntl.h> by <fcntl.h>.
> +
>  2020-01-06  Andrew Burgess  <andrew.burgess@embecosm.com>
>  
>  	* gdb.base/backtrace.c: New file.
> diff --git a/gdb/testsuite/gdb.base/fileio.c b/gdb/testsuite/gdb.base/fileio.c
> index 7f482a34d3..0f201518b7 100644
> --- a/gdb/testsuite/gdb.base/fileio.c
> +++ b/gdb/testsuite/gdb.base/fileio.c
> @@ -1,13 +1,12 @@
>  #include <stdio.h>
>  #include <stdlib.h>
>  #include <string.h>
> -#include <sys/errno.h>
>  #include <sys/types.h>
> -#include <sys/fcntl.h>
>  #include <sys/stat.h>
>  #include <sys/time.h>
>  #include <errno.h>
>  #include <sys/wait.h>
> +#include <fcntl.h>
>  #include <unistd.h>
>  #include <time.h>
>  /* TESTS :
> -- 
> 2.17.1

-- 
Joel


  reply	other threads:[~2020-02-01 10:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-02 14:47 Lukas Durfina
2020-01-05  6:25 ` Joel Brobecker
2020-01-07 13:48   ` Lukas Durfina
2020-01-07 17:55     ` Joel Brobecker
2020-01-09  8:17       ` Lukas Durfina
2020-02-01 10:15         ` Joel Brobecker [this message]
2020-02-03 10:00           ` Lukas Durfina
2020-02-03 10:25             ` Joel Brobecker
2020-02-03 10:10           ` [PATCH] [gdb/testsuite] Fix compilation error with musl in gdb/testsuite/gdb.base/fileio.c Lukas Durfina
2020-02-03 10:37             ` Joel Brobecker

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=20200201101548.GA19442@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ldurfina@tachyum.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