On Feb 11, 11:14 pm, Vyacheslav Akhmechet <[email protected]> wrote:
>
> I plan to merge with mainline branch eventually, but don't have the
> time to do it now. If nobody has the time to look through my fixes,
> please disregard this message :)

I'm going to pull everything right away except for:


http://bitbucket.org/coffeemug/weblocks-slava/changeset/c0f63e7cd805/
The browser-supplied name is not 8-bit safe due to a nasty bug in
librfc2388.
It needs to be modified with

(defun octet-string->utf-8 (s)
  "Kludge to fix librfc2388 bug."
  (sb-ext:octets-to-string
    (map '(vector (unsigned-byte 8)) #'char-int s)))


http://bitbucket.org/coffeemug/weblocks-slava/changeset/f9af7daa8e27/
Why are integer and float parser in parsers/common.lisp and not in
separate
files?


http://bitbucket.org/coffeemug/weblocks-slava/changeset/2a57103fa2e0/
Why do you make it statically depend on html-template?
What's wrong with asdf-system-connections?


http://bitbucket.org/coffeemug/weblocks-slava/changeset/434096153bf4/
What's going on here? The commit message isn't really helpful, and the
hunks
are pretty large. The last hunk is definitely a candidate, but I'd be
grateful
if you could tell me a bit about the others.


http://bitbucket.org/coffeemug/weblocks-slava/changeset/93642076d03c/
Hrm, not sure how that fix works/what cases it affects. Guess it's
another
one of those "oh no, we've been comparing pane-info, attributized,
symbol, cased string all wrong" nav things...


http://bitbucket.org/coffeemug/weblocks-slava/changeset/3bce46f60f71/
Won't pull, it's just a feature that will make the jwr merge harder.


Thanks!

  Leslie
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"weblocks" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to