libftdi Archives

Subject: Re: [PATCH] added function-call to access version information

From: Martin Zenzes <mzenzes@xxxxxxxxxxxxxxxxxxxxxxxx>
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Date: Fri, 09 Jul 2010 18:06:48 +0200
Hi Thomas,

> The fixed size array will not be enough if git is unable to come up with
> a short version of the md5 (f.e. if two md5 sums are close to each other).

Yeah, the fixed size itself if not fixed, depends on the output
generated by the script (which shoulb be a constant length string? At
least, the function could pad/cut the string to a constant length). But
8^26 seems like a huge number to identify a commit out of a fixed number
of commits (which won't be more that 10000). Collisions won't likely
happen, according to linus...

> I guess we can figure the shell script invocation out,
> though we shouldn't abort the build process if it fails (f.e. on Win32).

Hm no, that should not happen... 

> If the patch is for libftdi-1.x only, then yes.

Ok, but against which repo should I base my patch? As I'm fairly new,
I'm still confused about which one is "the" libftdi...

> Not only to new users ;) I'll send a separate mail about it,
> libftdi-1.x is the right time to deprecate autohell.

autohell? hm, you name it...


libftdi - see for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx   

Current Thread