From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753205AbcG2Q7M (ORCPT ); Fri, 29 Jul 2016 12:59:12 -0400 Received: from mail-it0-f41.google.com ([209.85.214.41]:36156 "EHLO mail-it0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751808AbcG2Q7K (ORCPT ); Fri, 29 Jul 2016 12:59:10 -0400 MIME-Version: 1.0 In-Reply-To: <20160729124443.GA3686@salo> References: <20160729064055.GB25331@x> <20160729101011.GA3469@salo> <20160729110426.GA2945@x> <20160729124443.GA3686@salo> From: Stefan Beller Date: Fri, 29 Jul 2016 09:59:08 -0700 Message-ID: Subject: Re: [ANNOUNCE] git-series: track changes to a patch series over time To: Richard Ipsum Cc: Josh Triplett , "git@vger.kernel.org" , "Linux-Kernel@Vger. Kernel. Org" , Dave Borowitz Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 29, 2016 at 5:44 AM, Richard Ipsum wrote: >> >> 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. > > Worth noting here that Gerrit's one patch per change format isn't > intrinsic to Notedb, since we just need to track the sha we want > to merge and optionally the branch we intend to merge into. Note that Gerrit started to lose the "one patch at a time" notion. It is possible to at least submit multiple changes coupled together (even across project boundaries) via the topic. Some sort of cover letter is missing though, that could be used e.g. for the merge commit.