4 Matching Annotations
- Aug 2022
It's a great way to test various limits. When you think about this even more, it's a little mind-bending, as we're trying to impose a global clock ("who is the most up to date") on a system that inherently doesn't have a global clock. When we scale time down to nanoseconds, this affects us in the real world of today: a light-nanosecond is not very far.
There are many questions we can ask and answer about branch names. Each one is specific to one particular repository because all branch names are local to that particular repository. Any changes anyone makes in that repository affect only that one repository, at least at the time they make them.
which assumption? well, people make the assumption that our local repo should know some fact about the remote repo, like its default branch, without actually asking the remote about itself
- interesting idea
- challenging one's assumptions
- considering the extreme case: long times
- taking things to extremes
- may be stale
- good point
- making too many assumptions
- interesting way of thinking about it
- Mar 2021
The Model macro literally does what our model! step did.
That information is not generally relevant. Only makes sense for someone who actually knew about or used the old interface.
The docs shouldn't assume you are an experienced user / a user of the previous version.
Would have been appropriate in a Changelog entry or announcement, but not in the general docs.
- Feb 2021