Lucas Seiki Oshiro <lucasseikioshiro@xxxxxxxxx> writes: [snip] > ## Feedback > > I would like to ask for your feedback on this proprosal, specially: > > - on deciding if the JSON and linewise plaintext formats are the really the best, > or if I should consider others (e.g. gitconfig syntax, NUL-terminated, etc) > > - on deciding how the fields will be specified. This "<category>.<format>" was > a first idea based on the JSON structure > > - about the JSON schema > > - about information that may be nice to include in the output of this command, > even if they are not currently retrieved by `rev-parse` > One thing I'd also like to see is some thought/documentation of what kind of information should go into this command and what shouldn't. For e.g. should number of references in a repo be part of this command, or the `git refs` command. More broadly, which subsystem information should be exposed via `git repo-info` and how do we draw that line. Mostly to not create a new `git rev-parse` alternative. > Thanks! > I've also gone ahead and reviewed the patches individually and left some comments. - Karthik
Attachment:
signature.asc
Description: PGP signature
