From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 634B892B for ; Fri, 29 Jul 2016 14:35:07 +0000 (UTC) Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [217.70.183.194]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4AE3B257 for ; Fri, 29 Jul 2016 14:35:06 +0000 (UTC) Date: Fri, 29 Jul 2016 07:34:59 -0700 From: Josh Triplett To: David Howells Message-ID: <20160729143459.GA11814@x> References: <20160729131151.GF4340@x> <20160729075039.GA26402@x> <30809.1469794812@warthog.procyon.org.uk> <1596.1469801212@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1596.1469801212@warthog.procyon.org.uk> Cc: ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [ANNOUNCE] git-series: track changes to a patch series over time List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, Jul 29, 2016 at 03:06:52PM +0100, David Howells wrote: > Josh Triplett wrote: > > > Note that git-series doesn't provide a quilt-style push/pop workflow, > > with applied and unapplied patches; it just looks at HEAD. > > Ah... In that case it's probably not a sufficient substitute for how I use > stgit. Fair enough. I normally manipulate patches via "git rebase -i". You could use the two together, though, if you'd like to track the history you've changed with stgit. You'd just need to make sure you'd applied all the patches before doing a git series commit. - Josh Triplett