After searching on lore.kernel.org, do you click through individual messages with such insightful subject lines as, "media: camss: Format configuration per hardware version," and, "rcar-vin: feature enhancement and fixes?" or do you read through the nested results, which on a test search related to a recent problem I had, gave me 2.5 MB of text across 74K lines?
Even then, I didn't find exactly what I wanted and would need to browse the kernel source (and will it be mainline or next?) and click through. The frontend for git.kernel.org does not have per-line blame (unless I missed it somewhere) so I have to checkout just to find the commit I want or browse the log until I find the changed line or hope that the expanded log is verbose enough to match my search term.
lkml.org is certainly no better, with no method of searching or grouping related topics.
Or... Do you refer to a third-party search engine doing the heavy lifting of indexing and deciding the relevance of a problem?
As opposed to most chat clients, where you just search and get a preview of all possible matches, and then go to that conversation. Sure, with Discord it involves opening the client and the potential for security mishaps and other problems of modern software (ads, useless features) but it is generally not difficult to search through a half-decent channel.
You get similar ease-of-use and searchability with a git repository with a half-decent frontend plus it makes it significantly easier to track proposals, changes, feature history, etc.
... except when a merge request or issue suddenly has more than 5 participants or a branch is building a new feature, where it then makes sense to take it to a chat where you get an instant notification and tight feedback loop between all participants, rather than rapid-fire updating the bug tracker and its associated merge request comments and the reported issues in a dependency's repo.
Gotta go; a coworker is asking me in the chat to push a fix to nightly.
After searching on lore.kernel.org, do you click through individual messages with such insightful subject lines as, "media: camss: Format configuration per hardware version," and, "rcar-vin: feature enhancement and fixes?" or do you read through the nested results, which on a test search related to a recent problem I had, gave me 2.5 MB of text across 74K lines?
Even then, I didn't find exactly what I wanted and would need to browse the kernel source (and will it be mainline or next?) and click through. The frontend for git.kernel.org does not have per-line blame (unless I missed it somewhere) so I have to checkout just to find the commit I want or browse the log until I find the changed line or hope that the expanded log is verbose enough to match my search term.
lkml.org is certainly no better, with no method of searching or grouping related topics.
Or... Do you refer to a third-party search engine doing the heavy lifting of indexing and deciding the relevance of a problem?
As opposed to most chat clients, where you just search and get a preview of all possible matches, and then go to that conversation. Sure, with Discord it involves opening the client and the potential for security mishaps and other problems of modern software (ads, useless features) but it is generally not difficult to search through a half-decent channel.
You get similar ease-of-use and searchability with a git repository with a half-decent frontend plus it makes it significantly easier to track proposals, changes, feature history, etc.
... except when a merge request or issue suddenly has more than 5 participants or a branch is building a new feature, where it then makes sense to take it to a chat where you get an instant notification and tight feedback loop between all participants, rather than rapid-fire updating the bug tracker and its associated merge request comments and the reported issues in a dependency's repo.
Gotta go; a coworker is asking me in the chat to push a fix to nightly.