On Thu, Sep 25, 2008 at 03:19:09PM +0200, Wincent Colaiuta wrote: > 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). In my queue and something I will hopefully get to submit tomorrow or at the beginning of next week is actually support for full-blown templating of gitweb pages (customization of the summary page, even adding extra project actions) based on gitconfig-style specification within the project HEAD. In its simplest variant, this could be used for including a README from the HEAD tree as well, I think. But it's in the same class as the git-gui support for the 'publish' dialog, something potentially useful for others, but not *universally* useful and in this case, unfortunately somewhat invasive. -- Petr "Pasky" Baudis People who take cold baths never have rheumatism, but they have cold baths. -- 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
