)]}'
{
  "log": [
    {
      "commit": "6591b493871cf9b17de2ba272edb8ab529a8058b",
      "tree": "981dacab445637a5b3e6125c4571b9633f9417d1",
      "parents": [
        "f0693c8bd5c50380b299e19d19e7640024640b42"
      ],
      "author": {
        "name": "Josh Triplett",
        "email": "josh@joshtriplett.org",
        "time": "Thu Aug 06 07:57:01 2009 -0700"
      },
      "committer": {
        "name": "Steven Rostedt",
        "email": "rostedt@goodmis.org",
        "time": "Wed Aug 26 00:32:04 2009 -0400"
      },
      "message": "tracing: Add vim script to enable folding for function_graph traces\n\nfunction_graph traces look like nested function calls, complete with\nbraces denoting the start and end of functions.  function-graph-fold.vim\nteaches vim how to fold these functions, to make it more convenient to\nbrowse them.\n\nTo use, :source function-graph-fold.vim while viewing a function_graph\ntrace, or use \"view -S function-graph-fold.vim some-trace\" to load it\nfrom the command-line together with a trace.  You can then use the usual\nvim fold commands, such as \"za\", to open and close nested functions.\nWhile closed, a fold will show the total time taken for a call, as would\nnormally appear on the line with the closing brace.  Folded functions\nwill not include finish_task_switch(), so folding should remain\nrelatively sane even through a context switch.\n\nNote that this will almost certainly only work well with a single-CPU\ntrace (e.g. trace-cmd report --cpu 1).  It also takes some time to run\n(a few seconds for a large trace on my laptop).  Nevertheless, I found\nit very handy to get an overview of a trace and then drill down on\nproblematic calls.\n\nSigned-off-by: Josh Triplett \u003cjosh@joshtriplett.org\u003e\nLKML-Reference: \u003c20090806145701.GB7661@feather\u003e\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\n"
    }
  ]
}