Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)

Hi Nicolas, On Tue, 19 Sep 2017, Nicolas Morey-Chaisemartin wrote: > Le 19/09/2017 à 17:43, Johannes Schindelin a écrit : > > > > C'mon, don't *try* to misunderstand me. > > > > Of course there need to be updates as to the state of patch series. > > > > It's just that mails only go *so* far when

Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)

Hi Jonathan, On Tue, 19 Sep 2017, Jonathan Nieder wrote: > Johannes Schindelin wrote: > > > To relate that, you are using a plain text format that is not well > > defined and not structured, and certainly not machine-readable, for > > information that is crucial for project management. > > > >

Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)

Le 19/09/2017 à 17:43, Johannes Schindelin a écrit : > > C'mon, don't *try* to misunderstand me. > > Of course there need to be updates as to the state of patch series. > > It's just that mails only go *so* far when you need to connect and > aggregate information. You need the connection between

Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)

Johannes Schindelin wrote: > What you need is a tool to aggregate this information, to help working > with it, to manage the project, and to be updated automatically. And to > publish this information continuously, without costing you extra effort. > > I understand that you started before GitHub

Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)

Hi, Johannes Schindelin wrote: > To relate that, you are using a plain text format that is not well defined > and not structured, and certainly not machine-readable, for information > that is crucial for project management. > > What you need is a tool to aggregate this information, to help

Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)

Hi Junio, On Tue, 19 Sep 2017, Junio C Hamano wrote: > Johannes Schindelin writes: > > >> Do you have a concrete suggestion to make these individual entries > >> more helpful for people who may want go back to the original thread > >> in doing so? In-reply-to: or

Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)

Johannes Schindelin writes: >> Do you have a concrete suggestion to make these individual entries more >> helpful for people who may want go back to the original thread in doing >> so? In-reply-to: or References: fields of the "What's cooking" report >> would not

Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)

Hi Junio, On Sat, 16 Sep 2017, Junio C Hamano wrote: > And as you alluded to, we may need to see if we can help making it > easier to do the latter when needed. That mistakes it for "Someone Else's Problem". > Johannes Schindelin writes: > > > That's what you are

Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)

Johannes Schindelin writes: > On Sat, 16 Sep 2017, Junio C Hamano wrote: > >> Johannes Schindelin writes: >> >> > If you want *contributors* to ping the thread themselves, how about >> > *posting your updates there, too*? >> >> I do not

Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)

Hi Junio, On Sat, 16 Sep 2017, Junio C Hamano wrote: > Johannes Schindelin writes: > > > If you want *contributors* to ping the thread themselves, how about > > *posting your updates there, too*? > > I do not understand this comment at all. That is what I and

Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)

Johannes Schindelin writes: > If you want *contributors* to ping the thread themselves, how about > *posting your updates there, too*? I do not understand this comment at all. That is what I and others already and always do by responding to the patches, and when

Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)

Hi Junio, On Thu, 24 Aug 2017, Junio C Hamano wrote: > Lars Schneider writes: > > > On 22 Aug 2017, at 21:56, Junio C Hamano wrote: > > > >> Here are the topics that have been cooking. Commits prefixed with > >> '-' are only in 'pu' (proposed

Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)

Lars Schneider writes: > On 22 Aug 2017, at 21:56, Junio C Hamano wrote: > >> Here are the topics that have been cooking. Commits prefixed with >> '-' are only in 'pu' (proposed updates) while commits prefixed with >> '+' are in 'next'. The ones

Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)

On 22 Aug 2017, at 21:56, Junio C Hamano wrote: > Here are the topics that have been cooking. Commits prefixed with > '-' are only in 'pu' (proposed updates) while commits prefixed with > '+' are in 'next'. The ones marked with '.' do not appear in any of > the integration

Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)

On 08/22, Junio C Hamano wrote: > > * bw/submodule-config-cleanup (2017-08-03) 17 commits > - submodule: remove gitmodules_config > - unpack-trees: improve loading of .gitmodules > - submodule-config: lazy-load a repository's .gitmodules file > - submodule-config: move submodule-config