[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4655B9C2.4050200@trash.net>
Date: Thu, 24 May 2007 18:13:54 +0200
From: Patrick McHardy <kaber@...sh.net>
To: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>
CC: hadi@...erus.ca, David Miller <davem@...emloft.net>,
Thomas Graf <tgraf@...g.ch>,
Herbert Xu <herbert@...dor.apana.org.au>,
netdev@...r.kernel.org, Sridhar Samudrala <sri@...ibm.com>,
"Kok, Auke-jan H" <auke-jan.h.kok@...el.com>,
Krishna Kumar2 <krkumar2@...ibm.com>, xma@...ibm.com
Subject: Re: [RESEND][PATCH] [NET_SCHED]make qdisc_restart more readable
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.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists