Re: [RFC/PATCH] Formatting variables in the documentation
- From
Jeff King <peff@peff.net>
- Date
- May 26, 2016, 16:23 UTC
- Message-ID
- <20160526162348.GA18210@sigill.intra.peff.net>
- In-Reply-To
- <xmqqmvncyera.fsf@gitster.mtv.corp.google.com>
On Thu, May 26, 2016 at 09:18:17AM -0700, Junio C Hamano wrote:
Show 8 quoted lines
> > 1. Somebody produces a patch flipping the default. The patch is > > trivial, but the commit message should tell why, and try to dig up > > any possible problems we might see (e.g., why wasn't this the > > default? Particular versions of tools? Some platforms?) > [...] > There was no particular "caveat" raised there to recommend against > using this on particular versions of tools or platforms. It was > inertia that has kept the new optional feature "optional".
Thanks for digging. That matches my recollection and the limited research I did more recently.
Show 6 quoted lines
> > 2. Assuming no problems, Junio merges the patch to "next". We get > > any reports of issues from people using "next" day-to-day. > > So I can do these steps myself up to this point. After waiting for > a few days to see if somebody else with better memory tells me what > I forgot, perhaps.
OK. I was trying to see if (1) could be low-hanging fruit for any of the newcomers, but at this point it probably makes sense for you to just write the patch.
-Peff