Hi Mike, This is exactly what I was asking for. Could you explain what do you mean by submitting a* new path*? Is what you illustrate below doable on current gerrit for iotivity? I tried submitting using different author name for a specific patch but gerrit always refuses the patch.
Best regards, Khaled On Fri, Jan 13, 2017 at 4:24 AM, Finch, Mike - Michael < mike.f.finch at lowes.com> wrote: > In allseen alliance we would routinely change author on a change and > submit a new path, each time the author changed a new sign off line was > added. this particular change had 31 patch sets and the commit message > looked like this: > > > SmartSpaces Operation interface definitions v1. > > Change-Id: I84c7a2abbcfef908c6a005a5f097256b93da69dd > Signed-off-by: Stefano Toppan <stefano.toppan at electrolux.it> > Signed-off-by: Dongwon Kim <dongwon00.kim at lge.com> > Signed-off-by: seungchul.han <seungchul.han at lge.com> > Signed-off-by: Mike Finch <mike.f.finch at lowes.com> > Signed-off-by: youngkyun.jin <youngkyun.jin at lge.com> > Signed-off-by: Stefano Toppan <stefano.toppan at electrolux.it> > Signed-off-by: seungchul.han <seungchul.han at lge.com> > Signed-off-by: Stefano Toppan <stefano.toppan at electrolux.it> > > > ________________________________________ > From: iotivity-dev-bounces at lists.iotivity.org [iotivity-dev-bounces at > lists. > iotivity.org] on behalf of Mats Wichmann [mats at wichmann.us] > Sent: Thursday, January 12, 2017 5:37 PM > To: Thiago Macieira; ??? (Uze Choi) > Cc: iotivity-dev at lists.iotivity.org > Subject: Re: [dev] visiting "how to use Gerrit" topic > > On 01/12/2017 01:30 PM, Thiago Macieira wrote: > > On quinta-feira, 12 de janeiro de 2017 17:35:42 PST ??? (Uze Choi) wrote: > >>> 6. Is there a policy on whether commits require a matching Jira ticket? > >>> Mandatory? Suggested? Completely optional? > >> > >> Current policy is that it's optional, except for during RC time. At that > >> time, every change to be accepted into the next RC needs to have a > matching > >> JIRA ticket of sufficient priority. RM and QA set the rules. > >> > >> [Uz] -> Better to put the jira code into commit title as rule in case > there > >> is associated jira. > > > > Agreed, but please emphasise the change, not the bug report. > > > > Correct: > > IOT-1234: Fix implementation of doodad that failed to frobniz correctly > > > > Bad: > > Fix bug IOT-1234 > > > > > > Thanks to all who have commented on this topic. Not sure quite how to > update the wiki page, I may make a copy and ask for reviews on that > before replacing the content of the current one. > > I didn't get there was any great way for multiple developers to > cooperate on one change, which was one direction the discussion went. > Did I miss something? > > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > NOTICE: All information in and attached to the e-mails below may be > proprietary, confidential, privileged and otherwise protected from improper > or erroneous disclosure. If you are not the sender's intended recipient, > you are not authorized to intercept, read, print, retain, copy, forward, or > disseminate this message. If you have erroneously received this > communication, please notify the sender immediately by phone (704-758-1000) > or by e-mail and destroy all copies of this message electronic, paper, or > otherwise. > > By transmitting documents via this email: Users, Customers, Suppliers and > Vendors collectively acknowledge and agree the transmittal of information > via email is voluntary, is offered as a convenience, and is not a secured > method of communication; Not to transmit any payment information E.G. > credit card, debit card, checking account, wire transfer information, > passwords, or sensitive and personal information E.G. Driver's license, > DOB, social security, or any other information the user wishes to remain > confidential; To transmit only non-confidential information such as plans, > pictures and drawings and to assume all risk and liability for and > indemnify Lowe's from any claims, losses or damages that may arise from the > transmittal of documents or including non-confidential information in the > body of an email transmittal. Thank you. > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170116/b1ebea77/attachment.html>
