Tomek CEDRO wrote:
> When the code is intergrated to OpenOCD master

I don't think it will be.. I understand that you feel like you wasted
a lot of time, but that's really your own fault for not working with
the community. *You* made the choice to spend a lot of time working
on your code, before you suggested anything to the greater OpenOCD
community. It makes no sense to include your result into OpenOCD
simply because you decided to take that risk. Same in every project.
Send perfect patches early - that keeps the feedback loop tight and
allows to you avoid risking wasted time.


> I will send a patch that lowers the translation of debug levels
> as you are not the first person that asked for it :-)

Why should this wait for anything, in particular why should it wait
for any other commits to be included into OpenOCD?

Do you understand what this means:

Create a new commit on the branch with your existing commits in
gerrit, and push that.

If not - please ask for explanation and clarification, it is critical
to understand how easy it is to work with branches in git.


I understand that Spencer is reworking your commits, and that you
don't neccessarily agree with what he is doing. You need to clear
that up with him, in order for your commits can be considered for
inclusion.

But regardless of Spencer's rework, you can push a new commit which
follows one of the patch sets that you have already pushed, even if
Spencer has pushed a later version of the patch set.


Many thanks for your continued efforts

//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

Reply via email to