The entries added to CHANGES since 8.0.276 looks a bit sparse when
compared to the actual commits. Should any of this get an entry?:
http://pike-librarian.lysator.liu.se/index.xml?m=pike.git&starttag=&start=July+5&end=today&branch=8.0&path=%21*%2Frefs%2Fheads*&message=&bugs=&user=&merges=on&templa
On Fri, May 6, 2016 at 9:29 AM, Lance Dillon wrote:
> Hmm, probably a typo, documentation says composited-changed for both gtk2
> and 3. Looks like it may have existed since 2.10. I think it probably
> hasn't been tested. There are a lot of signals that would be hard to test
> without a complex
Hmm, probably a typo, documentation says composited-changed for both gtk2 and
3. Looks like it may have existed since 2.10. I think it probably hasn't been
tested. There are a lot of signals that would be hard to test without a
complex test.
Sent from Yahoo Mail on Android
On Thu, May 5
Should any of the following have a CHANGES note?:
* ADT.Heap: Added low_peek().
* Fix GTK2.SourceBuffer undo/redo signal names
* Fix spelling of composite[d]_changed signal
- Is that an API change or where the signals not properly hooked up
before?
* Crypto/SSL
- There is a ton of Crypt
