Update to Jan 18 meeting decisions #60
Conversation
playing around display playing around display playing around display playing around display added more entries based on Dec 7 meeting fix typos added more entries based on Dec 7 meeting fix typos fix indentation fix typos fix typos
playing around display playing around display playing around display playing around display added more entries based on Dec 7 meeting fix typos added more entries based on Dec 7 meeting fix typos fix indentation fix typos fix typos
This removed/coalesced repeat entries
…irected-line-segment
|
I think I need to take a tutorial on using forks, but this shouldn't have conflicts -- I updated before I made changes. @davidcarlisle: can you resolve them -- I scanned through and you should just take all the incoming ones. Thanks. |
|
@NSoiffer I have been productively using I've been burned by diverging forks using merge back in the SVN days, and even though git does it substantially better, you can still rewrite history without realizing it. The rebase pain points are a little different, but they tend to mostly come up with long-lived branches that have strayed too far away from the mainline history. And a squash allows to avoid most of that pain as well (and github makes squashing easy from the UI here). For short-lived branches rebase works quite reliably. |
|
@NSoiffer git is happy, you might want to check that you are |
|
https://w3c.github.io/mathml-docs/intent-core-concepts/#calculus has lost its first column, presumably a yaml glitch I'll sort out locally |
No description provided.