FWIW, I only use "due-to" to signify I (being "dev") have had significant help from someone else. This may be a patch/ pull request, or an analysis /design suggestion or something else. I thought the intention of the due-to was to explicitly give credit to everyone who helped the dev. I use it in the hope it encourages people to keep contributing.
Sent from my iPhone > On 2016/08/27, at 8:04, Matt Sicker <[email protected]> wrote: > > We don't gpg-sign commits, so it wouldn't really matter. It's more useful in > larger projects where you have a hierarchy of project leaders involved. > >> On 26 August 2016 at 18:02, Gary Gregory <[email protected]> wrote: >> Are you suggesting we augment the changes.xml model to reflect the 3rd attr? >> >> G >> >>> On Fri, Aug 26, 2016 at 4:02 PM, Matt Sicker <[email protected]> wrote: >>> Git has 3 distinctions though: author, committer, and signed off by (which >>> is optional). >>> >>>> On 26 August 2016 at 18:00, Gary Gregory <[email protected]> wrote: >>>> Maybe we can use the dev attr for the person who commits and the due-to >>>> attr as the actual author; kind of like git's distinction. >>>> >>>> ? >>>> >>>> Gary >>>> >>>>> On Fri, Aug 26, 2016 at 3:52 PM, Matt Sicker <[email protected]> wrote: >>>>> What about when you collaborate with a contributor? For example, a >>>>> half-finished patch. >>>>> >>>>>> On 26 August 2016 at 17:47, Gary Gregory <[email protected]> wrote: >>>>>> Copy-paste. Would you rather it does not show up with a due-to? >>>>>> >>>>>> Gary >>>>>> >>>>>>> On Fri, Aug 26, 2016 at 3:05 PM, Ralph Goers >>>>>>> <[email protected]> wrote: >>>>>>> Gary, >>>>>>> >>>>>>> I am noticing that you have marked several items in changes.xml as >>>>>>> “due-to” yourself? Why are you doing that? Traditionally, we have >>>>>>> omitted that when a committer does the work as it shows up as you >>>>>>> making the commit in the report. >>>>>>> >>>>>>> Ralph >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: [email protected] >>>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> E-Mail: [email protected] | [email protected] >>>>>> Java Persistence with Hibernate, Second Edition >>>>>> JUnit in Action, Second Edition >>>>>> Spring Batch in Action >>>>>> Blog: http://garygregory.wordpress.com >>>>>> Home: http://garygregory.com/ >>>>>> Tweet! http://twitter.com/GaryGregory >>>>> >>>>> >>>>> >>>>> -- >>>>> Matt Sicker <[email protected]> >>>> >>>> >>>> >>>> -- >>>> E-Mail: [email protected] | [email protected] >>>> Java Persistence with Hibernate, Second Edition >>>> JUnit in Action, Second Edition >>>> Spring Batch in Action >>>> Blog: http://garygregory.wordpress.com >>>> Home: http://garygregory.com/ >>>> Tweet! http://twitter.com/GaryGregory >>> >>> >>> >>> -- >>> Matt Sicker <[email protected]> >> >> >> >> -- >> E-Mail: [email protected] | [email protected] >> Java Persistence with Hibernate, Second Edition >> JUnit in Action, Second Edition >> Spring Batch in Action >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory > > > > -- > Matt Sicker <[email protected]>
