From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: [RESEND][PATCH] [NET_SCHED]make qdisc_restart more readable Date: Thu, 24 May 2007 18:13:54 +0200 Message-ID: <4655B9C2.4050200@trash.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: hadi@cyberus.ca, David Miller , Thomas Graf , Herbert Xu , netdev@vger.kernel.org, Sridhar Samudrala , "Kok, Auke-jan H" , Krishna Kumar2 , xma@us.ibm.com To: "Waskiewicz Jr, Peter P" Return-path: Received: from stinky.trash.net ([213.144.137.162]:36853 "EHLO stinky.trash.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750735AbXEXQOH (ORCPT ); Thu, 24 May 2007 12:14:07 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Waskiewicz Jr, Peter P wrote: >>sigh. >>I wont be able to do this change until tonight or tommorow >>morning. I think the process i am using to re-generate >>patches maybe too consuming? >>Maybe you could offer some advice. Heres what i do: >>1. clone Daves latest tree localy >>2. clone another tree from that >>3. create patch on second clone >>4. compile; test;compile;test until looks reasonable 5. >>commit with the comments 6. submit 7. build other patches on >>top (example batching in this case) 8. feedback on patch >>comes back 9. Re-do steps #2-#6 >> >>My steps #2-#6 are expensive; is there a way to optimize that process? > > > [..] > > One tree, multiple branches, very quick to move between them, low > overhead. If this works for you, also look at stacked GIT (stg) for > pushing and popping patches from your tree - very handy. I have also found that stgit is a huge time saver, especially for making changes to patches or when dealing with many patches with interdependencies.