# So I should still apply 0001/replacement-0002/0003, and they # should still mesh nicely together, right?
Yeah, that's right :)
2011/9/1 skeezix skeezix@skeleton.org:
OKay, to be specific here..
Earlier email included patches 0001/0002/0003
Next email included redone patch 00002 --
So I should still apply 0001/replacement-0002/0003, and they should still mesh nicely together, right?
jeff
On Wed, 31 Aug 2011, Jari Vetoniemi wrote:
# Bleh, included the old patch... Sorry about that. # # 2011/8/31 Jari Vetoniemi mailroxas@gmail.com: # > Hey, # > Just noticed that the buffer freeing wasn't quite sane on the 0002 # > patch, so here is bit better version. # > # > Cheers. # > # > 2011/8/30 Jari Vetoniemi mailroxas@gmail.com: # >> Done and done, # >> Includes version patch, more leak fixes on libpnd and discovery test # >> leaks fixed. # >> You should get 0 bytes leaked when you run with valgrind. # >> # >> Cheers. # >> # >> 2011/8/30 Grazvydas Ignotas notasas@gmail.com: # >>> On Mon, Aug 29, 2011 at 10:06 PM, Jari Vetoniemi mailroxas@gmail.com wrote: # >>>> But yeah, I sorted it all out eventually. I agree on adding the # >>>> version information to the bottom of the struct, # >>>> heck there should not be even reason why the disco struct would not # >>>> give all the information from PND. # >>>> # >>>> But yeah, I'll lurk around and see what future holds. # >>> # >>> Well if you need those things for your stuff to work you should just # >>> patch them in now, otherwise lurking/waiting for someone else may get # >>> too close to infinite. Reworking those few patches to add stuff at the # >>> end and resending doesn't sound hard. # >>> # >> # > #
-- If everyone would put barbecue sauce on their food, there would be no war.