On Fri, Jul 20, 2018 at 12:35 PM Junio C Hamano <gits...@pobox.com> wrote:
> It is not like anybody (including me) needs realtime up-to-date I thought the same for a long time, but contributing to other projects showed me that this is not necessarily the case. Having a real time update, even if it would be just "your patch is labeled 'under discussion'" is beneficial as I would know where it is "in the system". In a way I'd compare our contribution process to having an incredible fine grained paper map. Most of the world moved on to digital maps, that zoom in on-demand. (C.f. spelling out "See banned.h for banned functions" in Documentation/CodingGuidelines is a fine grained detail that is not relevant for *most* of the contributions, but just burdens the bearer of the paper map with weight; if this hint is given dynamically by the compiler or build system at relevant times, it is much better; Regarding the real time aspect here, it is also very good comparison to maps: While I know how to read paper maps (or offline maps) and how to navigate my way, it sure is easier to just follow the online up-to-date navigation service, that tells me what to do. )
