Thanks. A few days ago, I sent different set of patches to improve the decoding of MIDI. Let me know if I should also re-send those using "git format-patch". Either way, the ones that follow will use "git format-patch" (unless I get deeper into the sigrok code, at which point I will consider the github option).
> Date: Sun, 21 Aug 2016 17:51:26 +0200 > From: [email protected] > To: [email protected] > CC: [email protected] > Subject: Re: [sigrok-devel] Improvements to sigrok-test building > > Hi, > > On Mon, Aug 15, 2016 at 09:50:44AM -0700, Chris Dreher wrote: >> [resending, looks like sourceforge and hotmail.com have a compatibility >> issue] >> >> Here is a proposed patch for improving building sigrok-test. Mainly, it >> just adds support for python 3.5 and updates the README. This fixes a >> few things that slowed me down getting the unit tests running. >> >> While >> I have been developing software for decades, I am new to the code >> submission process for sigrok. If I am not following the correct >> process, just let me know. I am hoping to contribute soon to the MIDI >> protocol decoder. > > Thanks, merged! > > I've split this into two commits and added your name etc. It usually > easiest if you clone the repo, commit your changes locally and then use > e.g. "git format-patch HEAD~1" or such to create patch files that you > can send to the mailing list. You can also just put your patches on > github and ping us here or on IRC for a review/merge. > > > Cheers, Uwe. > -- > http://hermann-uwe.de | http://randomprojects.org | http://sigrok.org
------------------------------------------------------------------------------
_______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
