it's rare to have our job done for us.
> That's why we write code.
>
> I'm sure people would be happy to help if you submitted patches to
> support --format=json.
>
> On Tue, Apr 18, 2017 at 3:44 AM, Fred .Flintstone wrote:
>> Well the easiest way to work wi
C Hamano wrote:
> "Fred .Flintstone" writes:
>
>> So I would either have to do:
>> git rev-list --all
>> Then iterate over each line and do git-cat-file commit .
>>
>> Or do:
>> git rev-list --all | git cat-file --batch
>>
>> If I
tarts.
JSON output would have been very handy.
On Mon, Apr 17, 2017 at 2:59 PM, Duy Nguyen wrote:
> On Mon, Apr 17, 2017 at 7:44 PM, Fred .Flintstone wrote:
>> So I did "git rev-list --all --pretty" and it looks like "git log".
>> Which outputs a human-r
serializable format like JSON or CSV or something. Maybe I want more
data than commit, auhor, date, subject and body?
On Mon, Apr 17, 2017 at 2:38 AM, Junio C Hamano wrote:
> Ævar Arnfjörð Bjarmason writes:
>
>> On Sat, Apr 8, 2017 at 6:07 PM, Fred .Flintstone wr
$ git log --format=json
[{
"commit": "64eabf050e315a4c7a11e0c05ca163be7cf9075e",
"tree": "b1e977800f40bbf6de906b1fe4f2de4b4b14f0fd",
"author": "Tux 1490981516 +0200",
"committer": "Tux 1490981516 +0200",
"message": "This is a test commit",
"long_message": "This explains in
5 matches
Mail list logo
