| | <<<Back 1 day (to 2018/08/02) | 20180803 |
| sebras | another batch of jbig2dec, it all clustered wee on watts/ergs. | 12:59.10 |
| kens | More ??? | 12:59.26 |
| chrisl | sebras: you said the other day you were done!! | 12:59.53 |
| sebras | yes, I still had a LARGE comment explaining the details of how the generic region decoder worked, so tor8 and me put that off until the end. | 13:00.45 |
| kens | Oh OK | 13:00.56 |
| sebras | and because I now had fixed some error handling ossfuzz had it easier to find another few issues in jbig2dec. all fixed now I hope. | 13:01.21 |
| kens | It'll be nice to have them all done before the release | 13:01.48 |
| sebras | when is the release? | 13:02.00 |
| kens | September some time | 13:02.10 |
| | I asked chrisl and he said before the staff meeting | 13:02.28 |
| | Damn you beat me to the push | 13:02.42 |
| | Now I have to rebase my tree | 13:02.50 |
| sebras | makes sense. I hope this is the last of it, but who knows what ossfuzz might find. | 13:02.55 |
| kens | For some reason msys Git is running really, really, slowly | 13:03.24 |
| | I may reboot this PC | 13:03.30 |
| | Ah that threat worked, now its repsonsive again | 13:04.22 |
| | sebras did you mean to push the commmit 'WIP .gitignore' ? | 13:09.58 |
| tor8 | kens: I'm going to venture no :) | 13:10.50 |
| kens | Yeah that was rather what I thought | 13:11.03 |
| | Do you want to fix it ? | 13:11.14 |
| tor8 | I think we'll need Robin's help to kick the cluster back into shape if we do force pushes | 13:12.22 |
| kens | Oh yes good point | 13:12.38 |
| chrisl | Well, .gitignore won't affect builds or anything, so just a normal push to resolve any issues would be fine | 13:15.06 |
| tor8 | chrisl: I thought force pushing confused the cluster as to where the 'master' was making a hash of things on subsequent pushes | 13:16.31 |
| chrisl | tor8: Yeh, it does - but I don't think we need a force push for just a gitignore faux pas | 13:17.25 |
| tor8 | chrisl: right. now I understand what you meant. | 13:17.50 |
| chrisl | FWIW, if we really want to, the instructions to deal with a force push are on the twiki - so we don't *need* Robin to do it | 13:18.11 |
| kens | Probably jst as well since he#'s off on vacation next week (I think its next week) | 13:18.51 |
| Robin_Watts | kens: At the end of next week, yes. | 13:25.29 |
| kens | Ah I was correct then | 13:25.40 |
| sebras | kens: ehm, no. | 13:34.15 |
| | kens: sorry, got two back to back phonecalls from dad/girldfriend. :( | 13:34.35 |
| kens | Maybe you would like to add a new commit to remove it ? sebras | 13:34.47 |
| sebras | kens: I'm still reading the logs, haven't you alreayd force pushed it away? | 13:35.15 |
| kens | Nope | 13:35.54 |
| | chrisl pointed out that since it doesn't harm anything you can just do a new commit | 13:36.09 |
| sebras | kens: ok. | 13:37.44 |
| | kens: fixed. | 13:38.27 |
| kens | thanks ! | 13:38.33 |
| sebras | kens: thanks for catching it. | 13:39.24 |
| kens | :-) It was the title..... | 13:39.59 |
| | Kind of stood out | 13:40.10 |
| | Forward 1 day (to 2018/08/04)>>> | |
Log of #ghostscript at irc.freenode.net.