[PATCH 0/2] git-candidate: git based patch tracking and review · Richard Ipsum <hidden> · 2016-06-15
[PATCH 2/2] contrib/git-candidate: Add README · Richard Ipsum <hidden> · 2016-06-15
Re: [PATCH 2/2] contrib/git-candidate: Add README · David Turner <hidden> · 2016-06-15
Re: [PATCH 2/2] contrib/git-candidate: Add README · Richard Ipsum <hidden> · 2016-06-15
Re: [PATCH 2/2] contrib/git-candidate: Add README · David Turner <hidden> · 2016-06-15
Re: [PATCH 2/2] contrib/git-candidate: Add README · Sebastian Schuberth <hidden> · 2016-06-15
[PATCH 1/2] contrib: Add git-candidate subcommand · Richard Ipsum <hidden> · 2016-06-15
Re: [PATCH 0/2] git-candidate: git based patch tracking and review · Michael Haggerty <hidden> · 2016-06-15
Re: [PATCH 0/2] git-candidate: git based patch tracking and review · Richard Ipsum <hidden> · 2016-06-15
Re: [PATCH 0/2] git-candidate: git based patch tracking and review · Jeff King <hidden> · 2016-06-15
Re: [PATCH 0/2] git-candidate: git based patch tracking and review · Jonathan Nieder <hidden> · 2016-06-15
Re: [PATCH 0/2] git-candidate: git based patch tracking and review · Dave Borowitz <hidden> · 2016-06-15
Re: [PATCH 0/2] git-candidate: git based patch tracking and review · Richard Ipsum <hidden> · 2016-06-15

Re: [PATCH 0/2] git-candidate: git based patch tracking and review

From: Dave Borowitz <hidden>
Date: 2016-06-15 23:07:21

On Tue, Dec 1, 2015 at 3:55 PM, Jonathan Nieder [off-list ref] wrote:

Cc-ing dborowitz, who has been working on storing Gerrit's code review
information in Git instead of a separate database (e.g., see [1]).

Thanks, we actually already had a thread going that I realize only in
retrospect did not include the git mailing list.