public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Eric Anholt <eta@lclark.edu>
To: devel@XFree86.Org
Cc: cygwin-xfree@cygwin.com
Subject: Re: Proper attribution of patches
Date: Tue, 23 Dec 2003 20:45:00 -0000	[thread overview]
Message-ID: <1072210853.814.33.camel@leguin> (raw)
In-Reply-To: <Pine.BSI.4.53.0312231429290.9637@mail.his.com>

On Tue, 2003-12-23 at 11:32, Thomas Dickey wrote:
> On Tue, 23 Dec 2003, Harold L Hunt II wrote:
> 
> > XFree86 should be taking care not to steal credit for our patches by
> > committing them without proper attribution.
> 
> your standards are inconsistent: your committing the change rather than
> offering commit access to someone who solved a problem that (according
> to the email thread) that had stopped you for some _months_ indicates
> that your whole aim on this is to get credit for yourself.
> 
> I noted that the comment in the code was properly attributed, no further
> action was needed.

I see only minor inconsitency on his part, that the original commit of
that code didn't attribute it to its author in the CVS logs, while at
least some other commits do note authors of patches.  However, he didn't
explicitly take credit for it, like you did in the ChangeLog, and his
announcement of new packages with those changes reflects the author
correctly.  I don't see Harold Hunt asking for his name to be on the
patch in any way, only the patch's author's name (the "members of the
Cygwin/X community" in the original mail).

The only responsible thing for you to do would be to correct the
ChangeLog to attribute it to the patch's author.

-- 
Eric Anholt                                eta@lclark.edu          
http://people.freebsd.org/~anholt/         anholt@FreeBSD.org



  parent reply	other threads:[~2003-12-23 20:19 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200312222110.hBMLAPRo087003@public.xfree86.org>
2003-12-23 19:32 ` Harold L Hunt II
2003-12-23 19:32   ` Thomas Dickey
2003-12-23 19:41     ` Harold L Hunt II
2003-12-23 19:58       ` Thomas Dickey
2003-12-23 19:59         ` Harold L Hunt II
2003-12-23 20:27           ` Thomas Dickey
2003-12-23 20:43             ` Harold L Hunt II
2003-12-23 20:47               ` Thomas Dickey
2003-12-23 21:07                 ` Harold L Hunt II
2003-12-23 21:38         ` Brian E. Gallew
2003-12-23 21:51           ` Frédéric L. W. Meunier
2003-12-23 21:39         ` Brian E. Gallew
2003-12-23 20:06       ` Thomas Dickey
2003-12-23 20:19         ` Harold L Hunt II
2003-12-23 20:52           ` Thomas Dickey
2003-12-23 21:19             ` Harold L Hunt II
2003-12-23 22:40               ` Thomas Dickey
2003-12-24  0:09                 ` Harold L Hunt II
2003-12-23 20:45         ` Eric Anholt [this message]
2003-12-23 20:49           ` Thomas Dickey
2003-12-23 21:19             ` Harold L Hunt II
2003-12-23 21:45               ` Thomas Dickey
2003-12-23 22:13                 ` Harold L Hunt II
2003-12-23 22:21           ` Thomas Dickey
2003-12-23 22:23             ` Harold L Hunt II
2003-12-23 21:19     ` Alan Hourihane
2003-12-23 21:20       ` Harold L Hunt II
2003-12-23 21:30       ` Thomas Dickey
2003-12-23 22:11         ` Harold L Hunt II
2003-12-23 22:34           ` Thomas Dickey
2003-12-23 23:48             ` Harold L Hunt II
2003-12-24  0:09               ` Thomas Dickey
2003-12-24  0:31                 ` Christopher Faylor
     [not found]   ` <20031223184838.H55176@xfree86.org>
2003-12-24  6:18     ` Harold L Hunt II
2003-12-23 20:45 Armbrust, Daniel C.
2003-12-24  2:04 ` Thomas Dickey
2003-12-24  8:23   ` Alec Mihailovs
2003-12-24 14:25     ` Frédéric L. W. Meunier
2003-12-24  7:34 Armbrust, Daniel C.

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=1072210853.814.33.camel@leguin \
    --to=eta@lclark.edu \
    --cc=cygwin-xfree@cygwin.com \
    --cc=devel@XFree86.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).