Hi Afif, On Sat, Dec 24, 2016 at 07:24:22AM -0800, Afif Elghraoui wrote: > > I have actually been working on this over the past few days. I keep > works-in-progress out of the master branch, so my work is in the branch > topic/blasr-5 [1] and I've been posting updates to the upstream bug > tracker to avoid duplication of efforts between here and upstream. I > hoped anyone taking a look here would first check the upstream bug > tracker. I'm really sad to see the duplication of effort when I was so > particular to make sure my work was pushed :(. Is there a way we can > avoid this in the future?
Its no real problem. I think it will not happen to frequently since the situation to save package for upcoming releases is only every second year - perhaps posting the fact you are working in a separate branch would help in such cases. Feel free to replace everything I did by your probably more advanced changes since you know the internals way better. I also do not consider my time terribly wasted since I know have some insight into these packages. > The reason I made a blasr upload yesterday was because I was advised > that it might fix a problem that was affecting pbhoney (after correcting > the command-line flags). I was going to continue testing today, now that > the upload has been installed in the archive, and report back to the > blasr upstream. That's fine. Kind regards Andreas. -- http://fam-tille.de