The presumption you're making is based on the fact that it is easy /for you/.
A valid reason is, for those that don't know what Fossil is, and what to understand the history of 9fans decision making, there is no way to know that decision was made, or why. D On Wed, May 15, 2024 at 12:07 PM hiro <23h...@gmail.com> wrote: > > In the commit messages is not sufficient, either. One still must search > through the commit messages and identify the branch/context/etc. Plus, you > have to /know/ about what you are looking for, if something was removed. A > separate document that outlines these removed/altered/added items, and the > rationale/context, would solve that. > > This separate document exists these days, that's what we call the > release, you can sometimes even get it in print-form IIRC as sl > compiles it into various digital and analog formats. > > Regardless of us seemingly being in agreement about this, finding a > commit that removes fossil in the git log is *easy*, and knowing what > you want to be looking for is definitely a prerequisite for looking > for it, so I cannot draw the conclusion for the reason you stated. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tad3dc0c93039a7d2-M435b857d58b79d576dd5d2bb Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
