Tomek CEDRO wrote: > I dont want to expand the code that you already consider obsolete
I don't consider your commits obsolete, but I consider ft2232 obsolete. > We have two choices now I guess: > > 1. Add my commits and mark ft2232 obsolete, then make last release > I prefer this approach and suggest this all the time. I don't think it makes sense to put out a release and then immediately start work on replacing code that was added just before the release. > 2. We reject/waste all my current work on swd and continue to work I guess that your work is not a complete waste. > on 0.x.y. Leave version numbers out of this for now, they just cause more confusion. (Because you mean something specific by 1.x.y, while I don't.) > This will not give working solution to the users for next few > months or years The current code is still both on repo.or.cz and in Gerrit, so anyone wanting to use that can still do it easily. > a lot more commits will show up than I have now proposed Don't push a large number of commits at once. Only push single or a few commits, as you create them. > lots of them will be a regression for some time Why would that be acceptable? .. What do you mean here actually? Regression sounds like you would make some change that causes a new problem in OpenOCD. I don't understand why you would do that? > Patches should be sent directly to gerrit Yes, ever since gerrit was introduced. > You seem to prefer this one..? Yes, I think it makes a lot more sense. //Peter ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
