From: Josh Triplett <josh@joshtriplett.org>
To: Richard Ipsum <richard.ipsum@codethink.co.uk>
Cc: git@vger.kernel.org, linux-kernel@vger.kernel.org, dborowitz@google.com
Subject: Re: [ANNOUNCE] git-series: track changes to a patch series over time
Date: Fri, 29 Jul 2016 04:04:26 -0700 [thread overview]
Message-ID: <20160729110426.GA2945@x> (raw)
In-Reply-To: <20160729101011.GA3469@salo>
On Fri, Jul 29, 2016 at 11:10:11AM +0100, Richard Ipsum 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.
Looks promising, though!
> There seem to be a number of us trying to solve this in our different ways,
> it would be great to coordinate our efforts.
These definitely seem like a family of related problems. I'd like to
use git-series as a format for storing iterations on things like GitHub
pull-requests or Gerrit patch versions (in the latter case, overcoming
Gerrit's limitations on only handling one patch at a time). Integrating
reviews with that seems helpful.
> The prototype library I have is partly the result of some discussion and work
> with the Gerrit folks, since they were thinking about this problem
> before I even started writing git-candidate, and solved it with Notedb.[5]
>
> Let me know if you'd like to work together on this,
I'd love to.
I'll be presenting git-series at LinuxCon North America; will you be
there by any chance? If not, perhaps we could meet by IRC or some other
medium and talk about this family of problems.
I hope to use git notes with git-series in the future, by putting
another gitlink under the git-series for notes related to the series.
I'd intended that for more persistent notes; putting them in the series
solves some of the problems related to notes refs, pushing/pulling, and
collaboration. Using notes for review comments makes sense as well,
whether in a series or in a separate ref.
> I've been considering taking the perl-notedb prototype and writing
> a C library for it with bindings for other languages (i.e. Rust).
A C library based on libgit2 seems like a good idea; ideally the
bindings could interoperate with git2-rs. (Alternatively, Rust can
*export* a C interface, so you could write directly with git2-rs. :) )
One of the items on my long-term TODO list is a completely federated
GitHub; I've been looking at other aspects of that, but federated
reviews/comments/etc seem critical to that as well.
- Josh Triplett
next prev parent reply other threads:[~2016-07-29 11:05 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 [this message]
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
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160729110426.GA2945@x \
--to=josh@joshtriplett.org \
--cc=dborowitz@google.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).