El 25/9/2008, a las 12:30, Jakub Narebski escribió:
This is yet another series of planned gitweb features. It expands more on new user-visible features than on improving gitweb code (therefore for example using Git.pm/Git::Repo, gitweb caching, and list form of open for pipelines are not mentioned here). Which tasks / features are most requested? Which tasks should be done first? What do you have on your gitweb TODO list?
One which I'm looking at doing is supporting reading the "README.html" from the tree indicated by the current HEAD instead of reading it from a file in the .git directory.
This should make tracking and updating such READMEs a little easier as all that'll be required is a "push" to advance the HEAD and the new README goes live.
Obviously, will have to make this optional and configurable. I'm thinking of providing a means of specifying the filename to look for (no filename, the default, means don't look), and also a setting to indicate the content type of the file (either plain text, which would be wrapped in a <pre></pre> block with HTML entities used where appropriate, or HTML which would be included verbatim).
Cheers, Wincent -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
