On Tue, Oct 26, 2010 at 11:02 AM, Øyvind Harboe <[email protected]> wrote: > On Tue, Oct 26, 2010 at 10:55 AM, Drasko DRASKOVIC > <[email protected]> wrote: >> On Tue, Oct 26, 2010 at 10:44 AM, Øyvind Harboe <[email protected]> >> wrote: >>> On Tue, Oct 26, 2010 at 10:34 AM, Drasko DRASKOVIC >>> <[email protected]> wrote: >>>> On Mon, Oct 25, 2010 at 8:47 PM, Øyvind Harboe <[email protected]> >>>> wrote: >>>>>> I am using openocd-0.4.0. >>>>> >>>>> Try the HEAD of the master branch. >>>> >>>> I can not, as I am creating patch for local use based on stable release. >>> >>> Rebase your changes to git master. Read up on the git documentation >>> on how to do this. This is an area where git shines! If you don't know how >>> to do this, then you should make the investment in learning this if you >>> want the help from the community. >> Although I love git very much, I do not want to do this. I am working >> on a patch that I can share with some people locally, and I can not >> make a patch on a master branch that constantly changes. > > In such cases, I think you'll be hard pressed to find help in the open > source community. If you show no intention of contributing back > to the community, that's a huge disincentive for the community > to work with you. I disagree on this, having a lot of experience in OS. Every bug pointed, discussed and "workarounded" or solved, and any information that can put some light on the problem are very helpful for all those who come up with the same problem. Working for the community is not only contribution of raw code, but more the right info that can be shared. Here I pointed the problem and gave some solutions. It's a mini-patch, if you like it - can be helpful for someone.
I have intention to share all innovative and useful stuff, as I always did, but at this particular case it is something very specific (custom FPGA design of JTAG interface on custom SoC) and will be totally uninteresting for OpenOCD community as no person would use it. > It sounds like you don't have experience with git rebasing, because > git rebase really makes working on top of the master branch > simple in most cases, besides it is simply not true that > OpenOCD master branch "constantly changes" these days in the > sense that it would be hard or cumbersome to develop and rebase > most feature branches on top of it. OK, I'll see about this. But I am convinced that it will be more easier for the most of the people to apply patch 6 months from now on a stable release, than to clone dev branches, rebase, integrate the changes etc... BR, Drasko _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
