Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1452383
| From | Josh Triplett <josh@joshtriplett.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [ANNOUNCE] git-series: track changes to a patch series over time |
| Date | 2016-07-29 13:10 +0200 |
| Message-ID | <s0dPY-3RZ-23@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 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
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