[prev in list] [next in list] [prev in thread] [next in thread] 

List:       libusb-devel
Subject:    Re: [libusb] Submitting patches
From:       Hans de Goede <hdegoede () redhat ! com>
Date:       2016-11-03 18:51:33
Message-ID: 90dd8c33-a08f-fd3f-ae72-17f138b22f2e () redhat ! com
[Download RAW message or body]

Hi,

On 02-11-16 18:08, Ludovic Rousseau wrote:
> 
> 
> 2016-11-02 17:54 GMT+01:00 David Grayson <davidegrayson@gmail.com \
> <mailto:davidegrayson@gmail.com>>: 
> 
> GitHub can generate patch emails for pull requests.  Just add ".patch" the URL when \
> you are looking at a pull request: 
> https://github.com/libusb/libusb/pull/220.patch \
> <https://github.com/libusb/libusb/pull/220.patch> 
> 
> It is even possible to get all the github PR directly in your own git local \
> repository as branches as described in https://gist.github.com/piscisaureus/3342247 \
>  I find it very convenient to (locally) review PR, maybe modify the commit message \
> and apply them using cherry-pick instead of merge.

Ack.

Thank you both for this, both very useful things to know. I've merged the patch now
and closed the pull-req :)

Regards,

Hans

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
libusb-devel mailing list
libusb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-devel


[prev in list] [next in list] [prev in thread] [next in thread]