On 08 Mar 01:22, Cédric Krier wrote:Hi,I just strated «grafting» changeset to series and I discover a side effect of the named branch. The hgroundup hook updates the old issue with branch backport information [1] which is great but it also makes roundup to set the status to chatting. I don't feel to go back to all «grafted» issue to reset the status to resolved. So I propose that the hgroundup hook set always the status of the issue to resolved. This means that when working on an issue which will require many changesets over a long period, the status should be reset to in-progress manually because it will be set to resolved on each commit. What do you think?By the way over past few months, I had only one issue where I push a changeset but did not want to resolve the issue. I think default behavior should match the major case.
I agree also, I just had the case today for the first time in months/years. -- Nicolas Évrard - B2CK SPRL E-mail/Jabber: nicolas.evr...@b2ck.com Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
signature.asc
Description: Digital signature
