On Tue, Feb 7, 2017 at 4:04 AM, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > Hi Junio, > > On Mon, 6 Feb 2017, Junio C Hamano wrote: > >> Christian Couder <christian.couder@xxxxxxxxx> writes: >> >> > There is also Junio's work on Bundle v3 that was unfortunately >> > recently discarded. Look for "jc/bundle" in: >> > >> > http://public-inbox.org/git/xmqq4m0cry60.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx/ >> > >> > and previous "What's cooking in git.git" emails. >> >> If people think it might be useful to have it around to experiment, I >> can resurrect and keep that in 'pu' (or rather 'jch'), as long as it >> does not overlap and conflict with other topics in flight. Let me try >> that in today's integration cycle. > > I would like to remind you of my suggestion to make this more publicly > visible and substantially easier to play with, by adding it as an > experimental feature (possibly guarded via an explicit opt-in config > setting). > > Ciao, > Johannes For making this more publicly visible, I want to look into publishing the cooking reports on the git-scm.com. Maybe we can have a "dev" section there, that has * a "getting started" section linking to Documentation/SubmittingPatches How to setup your travis * "current state of development" section e.g. the cooking reports, the release calender, description of the workflow (which branches do exist and serve which purpose), Most of the static information is already covered quite well in Documentation/ so there is definitively overlap, hence lots of links to the ground truth. The dynamic information however (release calender, cooking reports) are not described well enough in Documentation/ so I think we'd want to focus on these in that dev section.