libftdi Archives

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

From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Date: Thu, 29 Jan 2015 11:21:20 +0100
Hi Robin,

On 01/28/2015 06:41 PM, Robin Haberkorn wrote:
>> 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.
>>
> Yes, that's exactly what I mean. It's a little bit more convenient with
> Github and you get a ticket system. Sending "git-request-pull" mails or
> patches does of course work as well. It would also still work if you had
> a Github mirror. It would be just another way to receive contributions
> and draw attention to the project.
> But this is not very important to me. It was only a suggestion.

libftdi already has 62 contributors (see AUTHORS),
so I would say it's a pretty active project :)

The problem with github's ticket system and other
"convenience" features is the vendor lock-in. The easiest way
to send patches is to create them with "git format-patch" and friends.
That way the code changes can be reviewed on the mailinglist,
probably even offline once downloaded. The linux kernel is
developed this way, so it scales pretty good.

Unfortunately I can't do much work this week
since I have to stay in bed :( Sorry 'bout that.

Cheers,
Thomas


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

Current Thread