Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1452987
| From | Christian Couder <christian.couder@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [ANNOUNCE] git-series: track changes to a patch series over time |
| Date | 2016-08-01 07:10 +0200 |
| Message-ID | <s1dEd-1XU-1@gated-at.bofh.it> (permalink) |
| References | <s09Mm-12H-5@gated-at.bofh.it> <s0d3z-3ia-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Jul 29, 2016 at 12:10 PM, Richard Ipsum <richard.ipsum@codethink.co.uk> wrote: > On Thu, Jul 28, 2016 at 11:40:55PM -0700, Josh Triplett wrote: > [snip] >> >> 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.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[ANNOUNCE] git-series: track changes to a patch series over time Josh Triplett <josh@joshtriplett.org> - 2016-07-29 08:50 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Richard Ipsum <richard.ipsum@codethink.co.uk> - 2016-07-29 12:20 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Josh Triplett <josh@joshtriplett.org> - 2016-07-29 13:10 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Richard Ipsum <richard.ipsum@codethink.co.uk> - 2016-07-29 14:50 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Josh Triplett <josh@joshtriplett.org> - 2016-07-29 15:10 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Richard Ipsum <richard.ipsum@codethink.co.uk> - 2016-07-31 16:40 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Stefan Beller <sbeller@google.com> - 2016-07-29 19:00 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Richard Ipsum <richard.ipsum@codethink.co.uk> - 2016-07-31 16:20 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Christian Couder <christian.couder@gmail.com> - 2016-08-01 07:10 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Eric Wong <e@80x24.org> - 2016-08-01 10:10 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Josh Triplett <josh@joshtriplett.org> - 2016-08-01 11:00 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Richard Ipsum <richard.ipsum@codethink.co.uk> - 2016-08-01 12:00 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Eric Wong <e@80x24.org> - 2016-08-01 23:30 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Stephen Warren <swarren@wwwdotorg.org> - 2016-08-01 17:30 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Josh Triplett <josh@joshtriplett.org> - 2016-08-01 21:50 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Richard Ipsum <richard.ipsum@codethink.co.uk> - 2016-08-03 21:30 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Josh Triplett <josh@joshtriplett.org> - 2016-08-05 00:50 +0200
Re: [ANNOUNCE] git-series: track changes to a patch series over time Richard Ipsum <richard.ipsum@codethink.co.uk> - 2016-08-10 20:40 +0200
csiph-web