Is there a reason "README" heuristics have not been implemented yet? I realize no heuristic will be perfect, but I suggested an idea a while back that would satisfy the vast majority of cases. In cases where the heuristic does not suffice the extension would have priority and can still be used. So what's the downside? I don't see any and that's what I am wondering why this hasn't been implemented.
== Why do I care? I do not like putting extensions on my projects top document files (README, HISTORY, COPYING) . I have only done so in cases to appease how GitHub functions. But it's not nice to be forced into something to appease a development tool. I realize sometimes that is inescapable, but when possible the development tool should conform to how developers work, not the other way round. And for decades developers have been creating README files with no extensions. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
