Re: Feature request: --format=json
- From
- Fred .Flintstone <eldmannen@gmail.com>
- Date
- Apr 18, 2017, 08:44 UTC
- Message-ID
- <CAJgfmqXqfp3A+A74dfkKjQb_26ZNH9anY52-G2L5ipg=+6--2w@mail.gmail.com>
- In-Reply-To
- <xmqq60i2im72.fsf@gitster.mtv.corp.google.com>
Well the easiest way to work with that would be JSON. So the best would be if Git could output the data I want in JSON format. Then it would be easy for me to work with data.
With git rev-list and git-cat file, its not so easy to reliably parse that output.
On Tue, Apr 18, 2017 at 2:38 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 18 quoted lines
> "Fred .Flintstone" <eldmannen@gmail.com> writes: > >> So I would either have to do: >> git rev-list --all >> Then iterate over each line and do git-cat-file commit <commit-id>. >> >> Or do: >> git rev-list --all | git cat-file --batch >> >> If I do it in a batch, then it will be tricky to reliably parse since >> I don't know when the message body ends and when the next commit >> starts. >> >> JSON output would have been very handy. > > I am somewhat puzzled. I thought that you were trying to come up > with a way to produce JSON output and people are trying to help you > by pointing out tools that you can use for that.