On Tuesday, June 28, 2011 15:36:17 Jie Zhang wrote:
> On Tue, Jun 28, 2011 at 12:45 PM, Mike Frysinger wrote:
> > On Tuesday, June 28, 2011 10:26:35 Jie Zhang wrote:
> >> I would like to see this limit to be relaxed or removed. I have
> >> encountered this limit for several times. I also saw others
> >> encountered this limit in the past.
> > 
> > i'd rather not.  people sometimes hit this limit because they're doing
> > something wrong.  i certainly dont want to see an e-mail of 1MiB+ data
> > files coming across the list (this has come up before).
> 
> But currently the limit is only 100KB. How about relax it to 200KB.
> According to the statistics of all the patch emails of various mailing
> lists in my gmail box, 200KB should be a good limit for UrJTAG
> according to its project size.

i dont feel too strongly about this, so i'm fine with that

> > as long as the default case expands into the const lookup table, this
> > looks fine to me.
> 
> I don't understand this.

that hex.c has logic:
+#if HOST_CHARSET == HOST_CHARSET_ASCII
+
+const unsigned char _hex_value[_hex_array_size] =
...
+#else
... build _hex_value array at runtime ...
+#endif

the default behavior should be the first.
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
UrJTAG-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/urjtag-development

Reply via email to