From: Samuel Thibault <samuel.thibault@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Simon Marchi <simark@simark.ca>,
Thomas Schwinge <thomas@codesourcery.com>,
thomas@schwinge.name, bug-hurd@gnu.org
Subject: Re: [PATCH] hurd: Add shared mig declarations
Date: Sat, 30 May 2020 22:28:07 +0200 [thread overview]
Message-ID: <20200530202807.amiqned7zxnztl6h@function> (raw)
In-Reply-To: <7e0cf6ad-3540-7297-10b7-2c28b8d38816@redhat.com>
Pedro Alves, le sam. 30 mai 2020 20:51:17 +0100, a ecrit:
> On 5/30/20 7:23 PM, Samuel Thibault wrote:
> > +++ binutils-gdb/gdb/gnu-nat-mig.h
> > @@ -0,0 +1,33 @@
> > +/* Common things used by the various *gnu-nat.c files
> > + Copyright (C) 2020 Free Software Foundation, Inc.
> > +
> > + Written by Samuel Thibault <samuel.thibault@ens-lyon.org>
>
> Please don't take this the wrong way, but a while ago the
> GDB project (following Glibc's lead) decided that we would
> not add more "contributed by", "written by", etc. notes.
>
> See here <https://sourceware.org/gdb/wiki/ContributionChecklist#Attribution>
> and follow the link there for rationale.
Ah, I had read that part, and thought it was talking about the commit
log, I didn't notice it was talking about source files.
Sure I'll just drop it, I was just following the content of the existing
gnu-nat.c file.
Samuel
next prev parent reply other threads:[~2020-05-30 20:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 18:23 Samuel Thibault
2020-05-30 18:30 ` Samuel Thibault
2020-05-30 19:51 ` Pedro Alves
2020-05-30 20:28 ` Samuel Thibault [this message]
2020-05-31 1:51 ` Simon Marchi
2020-05-31 7:20 ` Samuel Thibault
2020-06-01 2:05 ` Simon Marchi
2020-06-01 7:54 ` Samuel Thibault
2020-06-01 16:33 ` Christian Biesinger
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=20200530202807.amiqned7zxnztl6h@function \
--to=samuel.thibault@gnu.org \
--cc=bug-hurd@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simark@simark.ca \
--cc=thomas@codesourcery.com \
--cc=thomas@schwinge.name \
/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