git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Dave Borowitz <dborowitz@google.com>
To: Richard Ipsum <richard.ipsum@codethink.co.uk>
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 09:53:53 -0500	[thread overview]
Message-ID: <CAD0k6qQBcfq0++d=-uyGpakmd+bsxuWYUWcn8auYJPy_HLddTg@mail.gmail.com> (raw)
In-Reply-To: <CAD0k6qRFPMZxLh4MtwkXwrk4GCjf64vWEd=9NPn-t_-uVHWz9g@mail.gmail.com>

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.

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.

>> If the gerrit folks could let me know what I need to do to get
>> these modifications merged, or else what we need to do to achieve
>> equivalent functionality I'd really appreciate it.
>>
>> Thanks again,
>> Richard Ipsum
>>
>> [1]: https://bitbucket.org/richardipsum/perl-notedb
>> [2]: https://gerrit-review.googlesource.com/#/c/73436/
>> [3]: https://gerrit-review.googlesource.com/#/c/73602/
>> [4]: https://xkcd.com/927/

  reply	other threads:[~2016-01-08 14:54 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 [this message]
2016-01-08 19:23     ` Richard Ipsum
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

  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='CAD0k6qQBcfq0++d=-uyGpakmd+bsxuWYUWcn8auYJPy_HLddTg@mail.gmail.com' \
    --to=dborowitz@google.com \
    --cc=ekempin@google.com \
    --cc=git@vger.kernel.org \
    --cc=richard.ipsum@codethink.co.uk \
    --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.
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).