From: Pedro Alves <palves@redhat.com>
To: John Baldwin <jhb@FreeBSD.org>,
gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: GDB attribution policy (Re: [PATCH v2 2/3] Add FreeBSD/mips architecture.)
Date: Tue, 10 Jan 2017 16:19:00 -0000 [thread overview]
Message-ID: <61e386a9-ad55-5d10-6309-dbe8c6f2102e@redhat.com> (raw)
In-Reply-To: <c450f453-d4fa-7389-304e-d52c99036ca0@redhat.com>
FYI, I've added this to the wiki now:
https://sourceware.org/gdb/wiki/ContributionChecklist#Attribution
Thanks,
Pedro Alves
On 12/16/2016 12:22 PM, Pedro Alves wrote:
> IMO, "contributed by" "written by", etc. attribution statements are best not
> added to source files, and are better placed in the "Contributors" node in
> the manual [1], which seems to exist exactly for this purpose.
>
> I see a few advantages:
>
> - It ends up surviving even if these new files are deleted in the future.
>
> - It's discoverable by end users too, unlike some comment deep in some
> source file.
>
> - Doesn't get inaccurate over time, as other contributors touch / rework / add
> to / mostly rewrite the code over the years, who understandably won't
> remember or won't feel comfortable with touching the original "written by"
> notes.
>
> For similar reasons, a few years back, glibc explicitly stopped accepting
> attribution statements in sources, as can be seen in their version of the
> contribution checklist [2]. I believe the discussion that led to that glibc
> policy started here [3].
>
> I've discussed this with other GDB maintainers off list and it seems
> there's general agreement to follow such a policy in GDB as well.
>
> [1] - https://sourceware.org/gdb/current/onlinedocs/gdb/Contributors.html#Contributors
> [2] - https://sourceware.org/glibc/wiki/Contribution%20checklist#Attribution
> [3] - https://sourceware.org/ml/libc-alpha/2012-04/msg00339.html
next prev parent reply other threads:[~2017-01-10 16:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 21:01 [PATCH v2 0/3] Add FreeBSD/mips targets to GDB John Baldwin
2016-12-06 21:01 ` [PATCH v2 1/3] Use the ELF class to determine the word size for FreeBSD core notes John Baldwin
2016-12-13 11:04 ` Nick Clifton
2016-12-23 20:35 ` John Baldwin
2016-12-06 21:01 ` [PATCH v2 2/3] Add FreeBSD/mips architecture John Baldwin
2016-12-08 18:47 ` Luis Machado
2016-12-08 20:08 ` John Baldwin
2016-12-08 20:13 ` Luis Machado
2016-12-09 19:02 ` John Baldwin
2016-12-16 12:22 ` GDB attribution policy (Re: [PATCH v2 2/3] Add FreeBSD/mips architecture.) Pedro Alves
2017-01-10 16:19 ` Pedro Alves [this message]
2016-12-06 21:01 ` [PATCH v2 3/3] Add native target for FreeBSD/mips John Baldwin
2016-12-08 18:53 ` Luis Machado
2016-12-08 20:09 ` John Baldwin
2016-12-08 20:15 ` Luis Machado
2016-12-16 12:50 ` [PATCH v2 0/3] Add FreeBSD/mips targets to GDB 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=61e386a9-ad55-5d10-6309-dbe8c6f2102e@redhat.com \
--to=palves@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.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