From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758209AbcHCTWV (ORCPT ); Wed, 3 Aug 2016 15:22:21 -0400 Received: from ducie-dc1.codethink.co.uk ([185.25.241.215]:33417 "EHLO ducie-dc1.codethink.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752270AbcHCTWT (ORCPT ); Wed, 3 Aug 2016 15:22:19 -0400 Date: Wed, 3 Aug 2016 20:12:02 +0100 From: Richard Ipsum To: Josh Triplett Cc: git@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [ANNOUNCE] git-series: track changes to a patch series over time Message-ID: <20160803191202.GA22881@salo> References: <20160729064055.GB25331@x> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160729064055.GB25331@x> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 28, 2016 at 11:40:55PM -0700, Josh Triplett wrote: > > 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. > One other nice thing I've noticed about this tool is the way series behave like regular git branches: I specify the name of the series and from then on all other commands act on that series until told otherwise. git-appraise looks as though it might also have this behaviour. I think it's a nice way to do it, since you don't generally perform more than one review simultaneously. So I may well use this idea in git-candidate if it's okay. :) I haven't found time to use the tool to do any serious review yet, but I'll try and post some more feedback when I do. Hope this helps, Richard