public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu> To: cygwin-xfree@cygwin.com Cc: devel@XFree86.Org Subject: Re: Proper attribution of patches Date: Tue, 23 Dec 2003 22:11:00 -0000 [thread overview] Message-ID: <3FE8B5C5.1060106@msu.edu> (raw) In-Reply-To: <Pine.BSI.4.53.0312231615380.28900@mail.his.com> Thomas Dickey wrote: > On Tue, 23 Dec 2003, Alan Hourihane wrote: > > >>Thomas, >> >>If you did get this code directly from Cygwin/X's tree then I'd of >>expected at least the credit to be apportioned to Harold at the very >>least, rather than putting your name against it. Ralf's name could have >>been corrected later, with a follow email from Harold. >> >>It's a simple change to put that right in the CHANGELOG. So I'll do that. > > > I had that on my next set of commits. Then why not say so earlier? > Except for the _XtInherit one, the > fixes were idiot-level ones that I fixed inline, compared to X.Org and > sync'd. So no credit is owed for those. I agree. > However, there's a chunk of ifdef's in config/cf that I intend to use, so > that merits a note. Fine with me. > It's not from "Cygwin/X" tree, but freedesktop.org - though of course I > did the proper research to see what the whole story was. Well, if you were referring to the freedesktop.org tree all along, then those commits were made by another developer when he imported the entire tree to synch with our old xoncygwin tree on SourceForge.net. > All of this got > my attention since the current cygwin/X packages are broken, as Harold is > well aware. Our packages are not broken, if you meant the version that we distribute. XFree86 proper does not currently have a Cygwin port maintainer; the packages are expected to be broken. Harold
next prev parent reply other threads:[~2003-12-23 21:38 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 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 [this message] 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=3FE8B5C5.1060106@msu.edu \ --to=huntharo@msu.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: linkBe 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).