From: Richard Ipsum <richard.ipsum@codethink.co.uk>
To: Dave Borowitz <dborowitz@google.com>
Cc: git <git@vger.kernel.org>, Stefan Beller <sbeller@google.com>,
Edwin Kempin <ekempin@google.com>
Subject: Re: Working towards a common review format for git
Date: Fri, 8 Jan 2016 19:23:39 +0000 [thread overview]
Message-ID: <20160108192339.GA3514@salo> (raw)
In-Reply-To: <CAD0k6qQBcfq0++d=-uyGpakmd+bsxuWYUWcn8auYJPy_HLddTg@mail.gmail.com>
On Fri, Jan 08, 2016 at 09:53:53AM -0500, Dave Borowitz wrote:
> On Fri, Jan 8, 2016 at 9:24 AM, Dave Borowitz <dborowitz@google.com> wrote:
> > On Fri, Jan 8, 2016 at 9:08 AM, Richard Ipsum
> > <richard.ipsum@codethink.co.uk> wrote:
> >> Hi,
> >>
> >> In a prior email I mentioned in passing a library I've been working
> >> on to try to reach a common format for storing review content in git:
> >> perl-notedb.[1]
> >>
> >> I'm making reasonable progress with this but my work has uncovered
> >> necessary (and trivial) modifications to Notedb, the first[2] is a
> >> trivial modification to ensure the 'Status' trailer gets written
> >> to the commit when a change's status changes.
> >
> > I would consider this a bugfix, and will respond on that review.
> >
> >> The second[3] is an RFC
> >> where I suggest adding a 'Commit' trailer so that it is always
> >> possible to reference the commit under review by its sha.
> >
> > I think this is probably fine but I'll have to think about it some more.
> >
> >> With these patches applied to gerrit it's possible for perl-notedb to parse
> >> all meta content from notedb and map it to the actual git content
> >> under review. However, my concern at present is that I'm already
> >> operating under a fork of notedb which defeats the objective of
> >> collaborating to produce a standard format, let's try to avoid[4]
> >
> > I hope I can assuage some of your concerns by saying that since Gerrit
> > notedb is such a work in progress, literally nobody is running it in
> > the wild, so even if the formats diverge temporarily I don't see it as
> > being a long-term issue. But thank you for caring about it, I do
> > appreciate your proactive considerations.
Thanks, that's good to know,
thanks also for reviewing the modifications I mentioned. :)
>
> You know what would probably also be a good idea would be to spec out
> the entire format in a standalone document. That way when Gerrit
> doesn't have something implemented, it's clear that Gerrit is wrong,
> not that it's trying to fork the format.
I think that would be good, I could attempt to write a spec for the format
and post it here for review? I expect I'll want to work a little more on
perl-notedb before I do that though.
next prev parent reply other threads:[~2016-01-08 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 14:08 Working towards a common review format for git Richard Ipsum
2016-01-08 14:24 ` Dave Borowitz
2016-01-08 14:53 ` Dave Borowitz
2016-01-08 19:23 ` Richard Ipsum [this message]
2016-01-08 19:26 ` Dave Borowitz
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=20160108192339.GA3514@salo \
--to=richard.ipsum@codethink.co.uk \
--cc=dborowitz@google.com \
--cc=ekempin@google.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
/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.