From: Christian Couder <christian.couder@gmail.com>
To: Richard Ipsum <richard.ipsum@codethink.co.uk>
Cc: Josh Triplett <josh@joshtriplett.org>, git <git@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
dborowitz@google.com, Omar Jarjur <ojarjur@google.com>,
Harry Lawrence <hazbo@gmx.com>
Subject: Re: [ANNOUNCE] git-series: track changes to a patch series over time
Date: Mon, 1 Aug 2016 07:04:15 +0200 [thread overview]
Message-ID: <CAP8UFD12Jk0s0HPPWS3CqFcB37gzhzZZi-V0PfqrRhZO4zhHOA@mail.gmail.com> (raw)
In-Reply-To: <20160729101011.GA3469@salo>
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.
next prev parent reply other threads:[~2016-08-01 5:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 6:40 [ANNOUNCE] git-series: track changes to a patch series over time Josh Triplett
2016-07-29 10:10 ` Richard Ipsum
2016-07-29 11:04 ` Josh Triplett
2016-07-29 12:44 ` Richard Ipsum
2016-07-29 13:00 ` Josh Triplett
2016-07-31 14:35 ` Richard Ipsum
2016-07-29 16:59 ` Stefan Beller
2016-07-31 14:09 ` Richard Ipsum
2016-08-01 5:04 ` Christian Couder [this message]
2016-08-01 7:55 ` Eric Wong
2016-08-01 8:59 ` Josh Triplett
2016-08-01 9:53 ` Richard Ipsum
2016-08-01 21:19 ` Eric Wong
2016-08-01 15:14 ` Stephen Warren
2016-08-01 18:37 ` Josh Triplett
2016-08-15 18:17 ` Simon Glass
2016-08-15 20:05 ` Josh Triplett
2016-08-03 19:12 ` Richard Ipsum
2016-08-04 22:40 ` Josh Triplett
2016-08-10 9:37 ` Richard Ipsum
2016-08-10 22:07 ` Josh Triplett
2016-08-11 6:23 ` Eric Wong
2016-08-24 10:56 ` Jakub Narębski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP8UFD12Jk0s0HPPWS3CqFcB37gzhzZZi-V0PfqrRhZO4zhHOA@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=dborowitz@google.com \
--cc=git@vger.kernel.org \
--cc=hazbo@gmx.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojarjur@google.com \
--cc=richard.ipsum@codethink.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.