> Could you please also amend the status (merged to master, merged to > next, under discussion) for each of these items? Ok! This may change until the GSoC submission deadline, but by now: - Microproject: merged to master - Merge Documentation: merged to master - Extra prefix flag: closed - Fix on git.github.io <http://git.github.io/>: merged to master - Driver for INI files: under discussion > This kind of information is exposed via git-rev-parse(1) already, see > the section "Options for Files". Thanks for your clarification! But still, I was discussing with people here at my university who deals directly with research on FLOSS repositories, is it worth to find other uses cases for this new command? > I generally recommend students to take on smaller batches of work that > can be submitted individually. The way it is structured now means that > you will end up with a single deliverable at the end of your project. > But structuring the project like that introduces a high risk that you > won't be able to land anything until the end of your project in case > there is a bigger discussion around parts of these patches. I see... After sending this first version I was thinking about it and it would be hard to test the functionalities without having the JSON serializer minimally working. I'll send another version, proposing smaller batches of work and writing a minimal serializer at the beginning of the project, improving with the new features. > Patrick Thanks for your time!
