On Sat, Jul 30, 2016 at 01:47:42AM -0400, Jeff King wrote: > On Fri, Jul 29, 2016 at 09:50:55PM -0700, Josh Triplett wrote: > > > I would propose the following then: > > > > - I'll write a patch adding a config option format.from, along with > > documentation, without changing the default. > > - The release notes for the version of git introducing that config > > option should mention, prominently, the plan to change the default in > > a future version of git. > > - A subsequent release can change the default. No major rush to do > > this. > > > > Does that sound reasonable? > > That sounds fine to me. > > I do have to admit that after reading through the "format.*" section of > git-config(1), there is quite a bit that is configurable in it. So > perhaps we do not need to be as careful about behavior changes as I > thought. > > So if you wanted to squish steps 2 and 3 together, that would also be OK > by me. I'll send two separate patches, and I'll leave it up to Junio whether to apply the second one right away or wait a release. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html