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 >> <http://www.manning.com/bauer3/> >> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> >> Spring Batch in Action <http://www.manning.com/templier/> >> 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 <http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
