More fixes for the new server. This time the BSD date doesn't work like the Linux date :/
New code to handle diff's of initial versions on branches.
More updates for the new server.
Update for new location of viewcvs.
Update for new webserver.
Nothing changed, I just want to log a relevant change...
This is the latest modification to cvs2cl, revision 2.38. This is an
old and outdatted version of cvs2cl, but it's what we're using right
now. I've got rid of unanimous tags in this change. The patch given
below is a complete diff from 2.38.
777c777,778
< $files = wrap ("\t", " ", "$files");
---
> # tdb: no-wrap shouldn't wrap ANYTHING!
> #$files = wrap ("\t", " ", "$files");
934c935,936
< if ((scalar (@qunkrefs)) > 1)
---
> # tdb: hacked to turn off the commondir feature
> if ((scalar (@qunkrefs)) < 0)
978c980,981
< my $everyone_has_this_tag = 1;
---
> # tdb: we don't want to have unanimous tags
> my $everyone_has_this_tag = 0;
1126c1129,1130
< $beauty .= ", ";
---
> # tdb: hacked to put a newline after each one
> $beauty .= ",\n";
1175c1179,1180
< $beauty = "* $beauty:";
---
> # tdb: hacked to remove the prefixed *
> $beauty = "$beauty:";
A fix for version numbers with more than two parts - ie. branches (1.2.1.2)
It seems showing branches isn't actually working.
Added section to deal with users who don't have an e-mail address. Without this the line doesn't get any special treatment, which doesn't look pretty!
Fixed the link to diffs when there was a tag associated with the commit.
Added option to show commits since a given date: cvslog.cgi?period=since&days=2001/12/09 It should be noted that the defintion of "since" in this case does NOT include the day given.
Bug which meant the cvs update wasn't correctly executed before generating the cvslog output.
Major changes:
- Now supports period=date&date=yyyy/mm/dd query strings.
- The files/logs section of each commit has been broken into two seperate bits.
- The filenames are linked to their relevant viewcvs page.
- The revisions are linked to their diffs, allowing one to see the changes a
certain commit has introduced.
- The log message itself has been unwrapped, for neatness.
Bugs:
- fails to know about "deleted" files. They simply show up as a new revision.
This is a fault in the underlying cvs2cl script.
Notes:
- This uses a modified version of cvs2cl. The diff is given here to avoid any
confusion as to what this script expects in the future.
777c777,778
< $files = wrap ("\t", " ", "$files");
---
> # tdb1: no-wrap shouldn't wrap ANYTHING!
> #$files = wrap ("\t", " ", "$files");
934c935,936
< if ((scalar (@qunkrefs)) > 1)
---
> # tdb1: hacked to turn off the commondir feature
> if ((scalar (@qunkrefs)) < 0)
1126c1128,1129
< $beauty .= ", ";
---
> # tdb1: hacked to put a newline after each one
> $beauty .= ",\n";
1175c1178,1179
< $beauty = "* $beauty:";
---
> # tdb1: hacked to remove the prefixed *
> $beauty = "$beauty:";
Looks a bit neater I think.
Some fixes to sort the colours of links.
Added the title and bottom in the correct fashion. This is inline with the i-scream layout and style.
Added the left bar to the commit logs.
Improved the resulting HTML, making it vaguely readable.
Slight alteration to ensure that it only one module is checked by fullcvsupdate.sh if it is specified in the query string.
Now accepts a module in the query string, should that be preferable.
Urg, yellow. No...
Some changes to layout, incorporated from a modified version by Paul ;-)
Uses the new script that fully checks out and updates a cvs local copy.
Now been "updated" to support some more funky features :) Firstly the output is grouped by module, making it clearer to see what commits belong where. Secondly, query strings allow you to specify the period, rather than just the current day that the old one did. This are: Current Day: period=today Current Week: period=thisweek Last n Days: period=days&days=n There are also subtle location changes to suit the location on the new webserver rather than raptor.
Best update the checked out copy before doing the cvs2cl.
Now use viewcvs instead.
Changed the title on the page.
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, select a symbolic revision name using the selection box, or choose 'Use Text Field' and enter a numeric revision.