lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 24 May 2007 18:13:54 +0200
From:	Patrick McHardy <>
To:	"Waskiewicz Jr, Peter P" <>
CC:, David Miller <>,
	Thomas Graf <>,
	Herbert Xu <>,, Sridhar Samudrala <>,
	"Kok, Auke-jan H" <>,
	Krishna Kumar2 <>,
Subject: Re: [RESEND][PATCH] [NET_SCHED]make qdisc_restart more readable

Waskiewicz Jr, Peter P wrote:
>>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

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists