So I've come around to not wanting a change ID header :) For the back- and forward-port use-case having commit subject conventions that make use of "ticket IDs" or similar is a 90% solution that many users have been living with for decades. Nico --
So I've come around to not wanting a change ID header :) For the back- and forward-port use-case having commit subject conventions that make use of "ticket IDs" or similar is a 90% solution that many users have been living with for decades. Nico --
|