From owner-freebsd-hackers@freebsd.org Thu Oct 11 15:55:51 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85BB210BEE85 for ; Thu, 11 Oct 2018 15:55:51 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1265E762B7 for ; Thu, 11 Oct 2018 15:55:50 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-RoutePath: aGlwcGll X-MHO-User: 187feee0-cd6e-11e8-af31-edadc92cdc1a X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 187feee0-cd6e-11e8-af31-edadc92cdc1a; Thu, 11 Oct 2018 15:55:40 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w9BFtbac017761; Thu, 11 Oct 2018 09:55:37 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1539273337.72469.57.camel@freebsd.org> Subject: Re: Sponsored by: in commit messages From: Ian Lepore To: Stefan Bethke , freebsd-hackers@FreeBSD.org Date: Thu, 11 Oct 2018 09:55:37 -0600 In-Reply-To: <4ACC0E9B-0DC1-4316-BACB-9EF6958ADFBA@lassitu.de> References: <4ACC0E9B-0DC1-4316-BACB-9EF6958ADFBA@lassitu.de> Content-Type: text/plain; charset="ASCII" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2018 15:55:51 -0000 On Thu, 2018-10-11 at 17:52 +0200, Stefan Bethke wrote: > Hi there, > > I just had another update to a port that I maintain committed. Thanks > for that! > > However, the commit message contains a Sponsored by line. I'm not > sponsored by that company, and neither is the upstream project, > AFAICT. > > What is the significance of this line? > > The port update was mainly mechanical, although it included adding a > vuxml entry. At any rate, the submission contained a more specifc > entry for vuxml than what got committed. So I'm wondering what the > sponsoring actually entails. > > From what I have observed over the years, Sponsored by has often > indicated significant contributions to important subsystems. Is this > impression misguided? Does it simply indicate that the committer > working on that commit on sponsored time, no matter the amount of > work? > > > Stefan > My guess would be that the committer does much of their work for a company or organization and has customized a local commit-message template to include the sponsor line automatically. -- Ian