Options:
Previous day, Next day
- # Session Start: Tue Sep 15 00:00:00 2015
- # Session Ident: #css
- # [00:53] * Joins: jdaggett (~jdaggett@public.cloak)
- # [01:35] * Joins: Florian (~Florian@public.cloak)
- # [01:37] * Joins: zcorpan (~zcorpan@public.cloak)
- # [01:38] * Quits: jdaggett (~jdaggett@public.cloak) (jdaggett)
- # [01:44] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # [01:46] * Quits: darktears (~darktears@public.cloak) ("Leaving...")
- # [01:59] * Joins: jdaggett (~jdaggett@public.cloak)
- # [02:09] <fantasai> plinss: Yeah, pushing second heads is definitely not blocked on the hg side
- # [02:09] * fantasai just did that twice today :(
- # [02:09] * fantasai needs to be more aggressive about rebasing
- # [02:35] <fantasai> dauwhe: Verdict on css-inline review?
- # [02:35] <fantasai> dauwhe: Anything left to do, or ready to publish?
- # [02:36] <fantasai> dauwhe: We gotta give the webmaster some specific instructions on shortnames and spec obsoletion
- # [02:36] <fantasai> this round
- # [02:37] <Florian> fantasai, dauwhe: I've got some info from Steve Z about how the multiple baseline tables work. Will forward, and you can decide if the spec still makes sense in that light or not. I assume it does, but maybe some tweaks are needed to make it clearer.
- # [02:37] <Florian> fantasai: oh wait, you were CCed already.
- # [03:01] <fantasai> :)
- # [03:02] <fantasai> I think it probably needs to hook into OT better, but that's mostly in the realm of 'dominant-baseline' details.
- # [03:02] * fantasai hasn't looked into it in detail
- # [03:03] <Florian> I think what it is the spec still makes sense, but maybe we're using pre-established terminology in subtly different ways, leading to confusion for people (like Steve) who're aware of the previous meaning.
- # [03:03] <fantasai> hm, looks like Tab and I updated our affiliation listings around the same time. Good times for bibliographers all around.
- # [03:04] <fantasai> Florian: Possibly. But what's definitely happening, from what I understand, is we're taking an effect that happens within a font and extrapolating it to also manage alignment across font runs
- # [03:04] <fantasai> Florian: So it may not be the terminology is wrong, but the definitions are incomplete
- # [03:07] <Florian> right. We're tying <new-behavior> to the dominant baseline, without mentioning that the concept of a dominant baseline pre-exixted and was used for <other-thing>. As far as I can tell, <new-behavior> and <old-thing> are perfectly orthogonal / compatible.
- # [03:08] * Quits: adenilson (~anonymous@public.cloak) (adenilson)
- # [03:08] <Florian> We may just need to mentin <old-thing> to avoid font-savvy people reacting by saying "that's not what dominant baselines are for".
- # [03:08] <Florian> s/mentin/mention/
- # [03:09] <fantasai> I don't think they're orthogonal
- # [03:09] <fantasai> I think they're doing the same exact thing, except one's scoped to the font and the other is scoped to CSS inline box layout
- # [03:09] <Florian> you're right, I miss-spoke. But they are non contradictory
- # [03:09] <fantasai> yes
- # [03:10] <Florian> (misspoke? mis-spoke? too many sses)
- # [03:10] <fantasai> misspoke :)
- # [03:11] <fantasai> mis and miss are two different morphemes
- # [03:11] <Florian> right. expect "mis" is related to the verb "to miss", which throws me off often enough.
- # [03:11] <fantasai> :)
- # [03:14] <Florian> Besides, miss-spoke sounds lovely :) But I don't want to create the impression that miss-speaking somehow relates to misspeaking :(
- # [03:15] * fantasai thoroughly confused now
- # [03:16] <fantasai> TabAtkins: I think bikeshed shouldn't be auto-linking to github for issue-tracking. We don't track issues there currently (though we may want to in the future)
- # [03:16] <Florian> miss-speaking => neologism for speaking in a lady-like fashion
- # [03:20] <fantasai> github's workflow is really weird when you have to reject a patch for more work (which is reasonably often in a real software project)
- # [03:21] <Florian> how is it weird?
- # [03:21] <fantasai> Let's say you fix complicated bug X with three layers of patches, A, B, and C.
- # [03:22] <fantasai> If I make review comments, then you add another patch D which mixes up the logical changesets, or you have to kill the pull request (and associated comments) and start over. At least that's what I understand.
- # [03:23] <fantasai> A system built around something like mercurial queues would work much better for this, because you can go back and revise the changesets in your queue.
- # [03:23] <fantasai> and then resubmit them for review.
- # [03:23] <fantasai> and if you're versioning the patch queue, you can even diff the patches and go back and forth there.
- # [03:23] <Florian> why can't you add patch D at the end of the branch, and push again?
- # [03:24] <Florian> the Pull request is automatically updated with the new commit
- # [03:24] <fantasai> You can, but then you've lost the organization of the patches
- # [03:24] <Florian> you mean it's not really patch D, but it's changing patch A to A'?
- # [03:25] <fantasai> Let's say A was removing bad code, B was setting up new APIs, and C was switching to those APIs throughout the code.
- # [03:25] <fantasai> Yeah
- # [03:25] <fantasai> If you fix errors in B and C with patch D, then when someone tries to understand what you did, it's all garbled up again
- # [03:25] <fantasai> after you did such a nice job keeping them neatly reviewable
- # [03:25] <Florian> There's always a tension between logical commits vs chronological commits. I tend to rewrite history like there's not tomorrow to get the best logical commits before I share them, but once I do, I switch to chronological
- # [03:26] <Florian> s/not/no/
- # [03:26] * Joins: zcorpan (~zcorpan@public.cloak)
- # [03:26] <fantasai> You me like there's no yesterday :)
- # [03:26] <Florian> :)
- # [03:26] <Florian> I wonder what happens if you rewrite history on that same branch, and then force-push. Does github show something that makes sense?
- # [03:26] <fantasai> queues lets you manage changesets without fully committing them
- # [03:27] <fantasai> No idea
- # [03:27] <fantasai> I haven't tried
- # [03:27] <fantasai> maybe it does something sane. That'd be nice
- # [03:28] <Florian> alternatively, you can point to the PR in the bug it's trying to fix, and if the one you send is rejected, you close it, create a new one (with clean logical commits), and point to that one as well from the bug.
- # [03:33] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # [04:01] * Joins: estellevw (~estellevw@public.cloak)
- # [04:26] <TabAtkins> fantasai: I still plan to add an "editor db" to Bikeshed, so auto-genned specs will get our most up-to-date affiliation.
- # [04:27] * fantasai just ran perl -pi -e
- # [04:27] <TabAtkins> fantasai: And I agree, probably best to omit the GH issue tracking for now, since there's no issues at all right now.
- # [04:27] <TabAtkins> I'll add it to our defaults.
- # [04:27] * fantasai thanks :)
- # [04:31] <TabAtkins> Hmmm, that's not actually possible right now, without killing the "inline in spec" link too.
- # [04:31] <TabAtkins> I'll have to fix this.
- # [04:31] <dauwhe> fantasai: starting to review now. Darned day job :(
- # [04:35] <TabAtkins> Florian: How to properly amend a PR http://blog.adamspiers.org/2015/03/24/why-and-how-to-correctly-amend-github-pull-requests/
- # [04:40] * Joins: dauwhe_ (~dauwhe@public.cloak)
- # [04:46] * Quits: dauwhe (~dauwhe@public.cloak) (Ping timeout: 180 seconds)
- # [04:49] <dauwhe_> fantasai: Not starting to review now. Can't pull from repo; can't even get to drafts.csswg.org :(
- # [04:53] * Joins: dauwhe (~dauwhe@public.cloak)
- # [04:53] * Quits: dauwhe_ (~dauwhe@public.cloak) (Client closed connection)
- # [05:14] * Joins: zcorpan (~zcorpan@public.cloak)
- # [05:21] * Quits: estellevw (~estellevw@public.cloak) ("Snuggling with the puppies")
- # [05:21] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # [05:49] * Joins: estellevw (~estellevw@public.cloak)
- # [06:15] * Quits: dauwhe (~dauwhe@public.cloak) (Client closed connection)
- # [06:16] * Joins: dauwhe (~dauwhe@public.cloak)
- # [06:31] * Quits: estellevw (~estellevw@public.cloak) ("Snuggling with the puppies")
- # [06:32] * Quits: dauwhe (~dauwhe@public.cloak) (Ping timeout: 180 seconds)
- # [06:56] * Joins: dauwhe (~dauwhe@public.cloak)
- # [07:03] * Joins: zcorpan (~zcorpan@public.cloak)
- # [07:10] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # [07:13] * Quits: dauwhe (~dauwhe@public.cloak) (Ping timeout: 180 seconds)
- # [07:36] * Joins: dauwhe (~dauwhe@public.cloak)
- # [07:44] * Quits: dauwhe (~dauwhe@public.cloak) (Ping timeout: 180 seconds)
- # [08:37] * Joins: dauwhe (~dauwhe@public.cloak)
- # [08:43] * Quits: myles (~Adium@public.cloak) ("Leaving.")
- # [08:44] * Quits: dauwhe (~dauwhe@public.cloak) (Ping timeout: 180 seconds)
- # [08:51] * Quits: rego (~smuxi@public.cloak) (Client closed connection)
- # [08:52] * Joins: zcorpan (~zcorpan@public.cloak)
- # [08:56] * Joins: antonp (~Thunderbird@public.cloak)
- # [08:59] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # [08:59] * Joins: rego (~smuxi@public.cloak)
- # [09:03] * Quits: rego (~smuxi@public.cloak) (Client closed connection)
- # [09:10] * Joins: rego (~smuxi@public.cloak)
- # [09:22] * Joins: zcorpan (~zcorpan@public.cloak)
- # [10:04] <Florian> Bert: https://lists.w3.org/Archives/Member/w3c-css-wg/2015JulSep/0210.html and https://lists.w3.org/Archives/Member/w3c-css-wg/2015JulSep/0213.html
- # [10:04] <Florian> What's the next step?
- # [10:12] <Florian> TabAtkins, fantasai: TL;DR: github does the right thing with force pushes, so just rewrite history, and (force) push again to the PR branch. Good to know.
- # [10:31] * Joins: lajava (~javi@public.cloak)
- # [10:40] * Joins: dauwhe (~dauwhe@public.cloak)
- # [10:47] * Quits: dauwhe (~dauwhe@public.cloak) (Ping timeout: 180 seconds)
- # [11:07] * Quits: jdaggett (~jdaggett@public.cloak) (jdaggett)
- # [11:27] * Joins: Ms2ger (~Ms2ger@public.cloak)
- # [11:40] * Joins: dauwhe (~dauwhe@public.cloak)
- # [11:48] * Quits: dauwhe (~dauwhe@public.cloak) (Ping timeout: 180 seconds)
- # [12:16] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [12:41] * Joins: dauwhe (~dauwhe@public.cloak)
- # [12:49] * Quits: dauwhe (~dauwhe@public.cloak) (Ping timeout: 180 seconds)
- # [13:08] * Quits: rego (~smuxi@public.cloak) (Client closed connection)
- # [13:16] * Joins: Florian (~Florian@public.cloak)
- # [13:20] * Joins: rego (~smuxi@public.cloak)
- # [13:23] * Quits: Florian (~Florian@public.cloak) (Ping timeout: 180 seconds)
- # [13:35] * Joins: jdaggett (~jdaggett@public.cloak)
- # [13:42] * Joins: dauwhe (~dauwhe@public.cloak)
- # [13:49] * Quits: dauwhe (~dauwhe@public.cloak) (Ping timeout: 180 seconds)
- # [14:00] * Joins: Florian (~Florian@public.cloak)
- # [14:02] * Joins: plh (plehegar@public.cloak)
- # [14:05] * Quits: jdaggett (~jdaggett@public.cloak) (jdaggett)
- # [14:05] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [14:08] * Joins: dauwhe (~dauwhe@public.cloak)
- # [14:09] * Joins: dauwhe_ (~dauwhe@public.cloak)
- # [14:09] * Quits: dauwhe (~dauwhe@public.cloak) (Client closed connection)
- # [14:24] * Quits: rego (~smuxi@public.cloak) (Client closed connection)
- # [14:31] * Joins: rego (~smuxi@public.cloak)
- # [14:46] * Joins: Florian (~Florian@public.cloak)
- # [15:03] * Joins: dbaron (~dbaron@public.cloak)
- # [15:35] * Quits: Ms2ger (~Ms2ger@public.cloak) ("Leaving")
- # [15:35] * Joins: Ms2ger` (~Ms2ger@public.cloak)
- # [16:54] * Joins: adenilson (~anonymous@public.cloak)
- # [17:05] * Quits: dauwhe_ (~dauwhe@public.cloak) ("")
- # [17:15] * Quits: dbaron (~dbaron@public.cloak) ("8403864 bytes have been tenured, next gc will be global.")
- # [17:42] * Joins: dauwhe (~dauwhe@public.cloak)
- # [18:13] * Quits: Rossen_ (~Rossen@public.cloak) ("Page closed")
- # [18:19] * Joins: estellevw (~estellevw@public.cloak)
- # [18:29] * Quits: estellevw (~estellevw@public.cloak) ("Snuggling with the puppies")
- # [18:31] * Joins: myles (~Adium@public.cloak)
- # [18:54] * Joins: antonp1 (~Thunderbird@public.cloak)
- # [18:54] * Joins: tantek (~tantek@public.cloak)
- # [19:01] * Quits: antonp (~Thunderbird@public.cloak) (Ping timeout: 180 seconds)
- # [19:01] * antonp1 is now known as antonp
- # [19:02] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [19:04] * Quits: Ms2ger` (~Ms2ger@public.cloak) (Ping timeout: 180 seconds)
- # [19:13] * Joins: Ms2ger` (~Ms2ger@public.cloak)
- # [19:18] * Quits: myles (~Adium@public.cloak) ("Leaving.")
- # [19:33] * Joins: dbaron (~dbaron@public.cloak)
- # [19:39] * Quits: Ms2ger` (~Ms2ger@public.cloak) (Ping timeout: 180 seconds)
- # [19:49] * Joins: bkardell_ (~uid10373@public.cloak)
- # [19:49] <dbaron> TabAtkins, https://github.com/w3ctag/spec-reviews/issues/71 -- TAG can't find the spec
- # [19:49] <dbaron> (although we're not sure what review is needed)
- # [19:52] <dbaron> found it now
- # [19:52] * Joins: darktears (~darktears@public.cloak)
- # [19:54] * Joins: myles (~Adium@public.cloak)
- # [20:08] * Quits: lajava (~javi@public.cloak) (Ping timeout: 180 seconds)
- # [20:58] * Quits: Hamatti (~jumasan@public.cloak) (Ping timeout: 180 seconds)
- # [21:32] * Joins: glazou (~glazou@public.cloak)
- # [21:34] * fantasai waves to glazou
- # [21:35] <glazou> hellllo my dear :-d
- # [21:42] <fantasai> glazou: you doing okay?
- # [21:50] * Quits: tantek (~tantek@public.cloak) (tantek)
- # [22:23] * Quits: glazou (~glazou@public.cloak) (glazou)
- # [22:51] <fantasai> TabAtkins: Something's broken in bikeshed https://validator.w3.org/nu/?doc=https%3A%2F%2Fdrafts.csswg.org%2Fcss-inline%2F
- # [22:51] <fantasai> TabAtkins: It's generating weirdly invalid markup
- # [22:52] <fantasai> TabAtkins: nm, found the problem
- # [22:54] <TabAtkins> Weirdly invalid input does generate weirdly invalid output, yes.
- # [23:05] <fantasai> :)
- # [23:05] <fantasai> plinss: Can you do something about drafts.csswg.org/robots.txt ?
- # [23:05] <fantasai> plinss: I can't run the link checker on any of our documents, which is a problem
- # [23:06] <plinss> fantasai: yeah, but I need to disable the spamot defenses first, will do after the tag f2f
- # [23:06] <fantasai> Okay
- # [23:07] * fantasai tosses a copy of the impending WD onto her server for link checking
- # [23:28] * Quits: dbaron (~dbaron@public.cloak) (Ping timeout: 180 seconds)
- # [23:50] * Quits: plh (plehegar@public.cloak) ("Leaving")
- # [23:59] * Quits: abucur___ (~sid19072@public.cloak) ("Connection closed for inactivity")
- # [23:59] * Quits: cabanier (~sid15093@public.cloak) ("Connection closed for inactivity")
- # Session Close: Wed Sep 16 00:00:00 2015
Previous day, Next day
Think these logs are useful? Then please donate to show your gratitude (and keep them up, of course). Thanks! — Krijn