Thread (23 messages) 23 messages, 8 authors, 2016-08-24

Re: [ANNOUNCE] git-series: track changes to a patch series over time

From: Christian Couder <hidden>
Date: 2016-08-01 05:04:23
Also in: lkml

On Fri, Jul 29, 2016 at 12:10 PM, Richard Ipsum
[off-list ref] wrote:
On Thu, Jul 28, 2016 at 11:40:55PM -0700, Josh Triplett wrote:
[snip]
quoted
I'd welcome any feedback, whether on the interface and workflow, the
internals and collaboration, ideas on presenting diffs of patch series,
or anything else.
This looks awesome!

I've been working on some similar stuff for a while also.[1][2]

I'm particularly interested in trying to establish a standard for
storing review data in git. I've got a prototype for doing that[3],
and an example tool that uses it[4]. The tool is still incomplete/buggy though.
There is also git-appraise (https://github.com/google/git-appraise)
written in Go to store code review data in Git.
It looks like it stores its data in git notes and can be integrated
with Rust (https://github.com/Nemo157/git-appraise-rs).
There seem to be a number of us trying to solve this in our different ways,
it would be great to coordinate our efforts.
Yeah, I agree.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help