libftdi Archives

Subject: Re: [PATCH] ftdi_eeprom: reliable device selection and flashing of new VID/PIDs

From: Paul Fertser <fercerpav@xxxxxxxxx>
To: Robin Haberkorn <haberkorn@xxxxxxxxxxxx>
Cc: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Date: Wed, 28 Jan 2015 09:42:20 +0300
Hi,

On Tue, Jan 27, 2015 at 11:21:17PM +0100, Robin Haberkorn wrote:
> btw.: Hosting a Github mirror of the libftdi repository could boost free
> software contributions to libftdi. With a Github repository, I could
> create a fork and maintain my "patches" on a public branch, while
> sending you pull requests.

How is it different from the current situation? Anybody can fork
current git repo, maintain public branches anywhere he or she would
prefer and send pull requests.

Unless when you say "pull request" you do not mean git-request-pull(1)
but the unique non-standard proprietary github "pullrequest" which
would force the maintainers to use github webui to do their work and
depend on a single commercial entity.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@xxxxxxxxx

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx   

Current Thread