From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 8644@debbugs.gnu.org
Subject: bug#8644: font-locking of multi-author changelog entries
Date: Tue, 10 May 2011 22:31:02 +0200 [thread overview]
Message-ID: <BANLkTikN4dKEPWiOo0qU_DUn7Z3KwcfSyw@mail.gmail.com> (raw)
In-Reply-To: <83oc3agvjx.fsf@gnu.org>
On Tue, May 10, 2011 at 22:17, Eli Zaretskii <eliz@gnu.org> wrote:
> I never really understood the need for these entries. How can two or
> more people write some piece of code?
You just denied the XP practice of "pair programming"... :-)
> Ideas cannot be copyrighted, so
> only the one who wrote the final version should be named, the rest can
> be attributed as "suggested by" or whatever.
That depends on how much was done by the other people. Sometimes the
one who didn't code a line did all design decisions. "Suggested by"
does not cover it IMHO.
Juanma
next prev parent reply other threads:[~2011-05-10 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 19:39 bug#8644: font-locking of multi-author changelog entries Glenn Morris
2011-05-10 20:17 ` Eli Zaretskii
2011-05-10 20:31 ` Juanma Barranquero [this message]
2011-05-10 20:38 ` Eli Zaretskii
2011-05-11 16:20 ` Richard Stallman
2011-05-10 22:55 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTikN4dKEPWiOo0qU_DUn7Z3KwcfSyw@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=8644@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).