|
|||||||||||||||||||||||||||
> > 2 - When cvs2html discovers subdirs then it will make html > for those as > > well. Good. Why doesn't it produce links from the "main" > html to the subdir > > "html"? > > I dont fully understand this. Please make an > explicit example. This is possibly linked to (3). I had problems running cvs2html on several modules. I have now been successfull in running cvs2html on a module with subdirs. And the links are there - sorry for the inconvinience. > > 3 - cvs2html will fail "Error 4 : Doing .: Log is empty." > if the root dir is > > empty except for subdirs. Is this intentional? > > Actually this is a problem - I have applied your patch > from today, check if things are better now. And actually my patch only filters empty lines in the log output - or to be exact - lines containing only spaces. I don't think it helps the empty-root-dir-problem. I might investigate the latter and send a patch at some point in the future. But for that I think I _will_ have to learn Perl ;) > http://cvs.sslug.dk/cvs2html/ has the new code :) Cool! > > And the most important one: > > 4 - I _really_ need an automated release note generator. You know, a > > script that collects all log entries between two tags, or > from some tag > > until current version, and puts it in one file. Is that > what 'cvs2html -r' > > is supposed to do? Any other ways to do this? > > cvs2html -rREV1:REV2 should do the trick - not true?? It works for me too now :) I had a few modules that just did _not_ work well with cvs2html. When I understand what went wrong, I will send patches (if needed). And thanks again for a super cool tool - it was actually exactly what I have been looking for for a looong time - and then some. :D Holger Bille
|
||||||||||||||
|
||||||||||||||