I haven't used the parallel-wget branch as yet. I made an attempt some time ago, but found that the documentation was lacking and I had no idea on how to proceed with using the threads and metalink features. I'll give it another shot now and see if I can get it working.
Though as long as we're not breaking the stable release when threads and metalink are disabled, I don't see any harm in merging the branch into master. On Tue, Jul 2, 2013 at 3:21 PM, Giuseppe Scrivano <[email protected]> wrote: > Hi, > > I would like to merge the parallel-wget branch into master. I already > merged master into parallel-wget, so it should be a no-op and make > master look identical to parallel-wget as it is now. > > The idea is that the new features (threads and metalink) are not enabled > by default, but must be forced at configure time so not to break the > stable release of wget, but I don't know how much this is true as there > are many changes. > > The code introduces some hacks, but I think we can deal with this for > now and refactor the code once it is on master, not much happened this > last year when we had the project on a different branch. > > Is anyone against this? > > -- > Giuseppe > > -- Thanking You, Darshit Shah
