Fossil SCM
Remove deprecated <center> tags.
Commit
d57f2395709a42c42f96a34f2277951a520c0459
Parent
5853fcf132800f9…
14 files changed
+4
-4
+6
-4
+10
+2
-2
+1
-1
+11
-10
+1
-3
+2
-2
+1
-1
+7
-9
+1
-3
+1
-3
+2
-2
+1
-2
+4
-4
| --- src/stat.c | ||
| +++ src/stat.c | ||
| @@ -412,13 +412,13 @@ | ||
| 412 | 412 | ); |
| 413 | 413 | } |
| 414 | 414 | fsize = file_size(g.zRepositoryName); |
| 415 | 415 | approxSizeName(sizeof(zBuf), zBuf, fsize); |
| 416 | 416 | @ <h2>Repository Size: %s(zBuf)</h2> |
| 417 | - @ <center><svg width='800' height='500'> | |
| 417 | + @ <svg class="statistics-report-pie-chart" width='800' height='500'> | |
| 418 | 418 | piechart_render(800,500,PIE_OTHER|PIE_PERCENT); |
| 419 | - @ </svg></center> | |
| 419 | + @ </svg> | |
| 420 | 420 | |
| 421 | 421 | if( g.localOpen ){ |
| 422 | 422 | db_multi_exec( |
| 423 | 423 | "DROP TABLE temp.dbx;" |
| 424 | 424 | "CREATE VIRTUAL TABLE temp.dbx USING dbstat(%s);" |
| @@ -441,11 +441,11 @@ | ||
| 441 | 441 | ); |
| 442 | 442 | } |
| 443 | 443 | fsize = file_size(g.zLocalDbName); |
| 444 | 444 | approxSizeName(sizeof(zBuf), zBuf, fsize); |
| 445 | 445 | @ <h2>%h(file_tail(g.zLocalDbName)) Size: %s(zBuf)</h2> |
| 446 | - @ <center><svg width='800' height='500'> | |
| 446 | + @ <svg class="statistics-report-pie-chart" width='800' height='500'> | |
| 447 | 447 | piechart_render(800,500,PIE_OTHER|PIE_PERCENT); |
| 448 | - @ </svg></center> | |
| 448 | + @ </svg> | |
| 449 | 449 | } |
| 450 | 450 | style_footer(); |
| 451 | 451 | } |
| 452 | 452 |
| --- src/stat.c | |
| +++ src/stat.c | |
| @@ -412,13 +412,13 @@ | |
| 412 | ); |
| 413 | } |
| 414 | fsize = file_size(g.zRepositoryName); |
| 415 | approxSizeName(sizeof(zBuf), zBuf, fsize); |
| 416 | @ <h2>Repository Size: %s(zBuf)</h2> |
| 417 | @ <center><svg width='800' height='500'> |
| 418 | piechart_render(800,500,PIE_OTHER|PIE_PERCENT); |
| 419 | @ </svg></center> |
| 420 | |
| 421 | if( g.localOpen ){ |
| 422 | db_multi_exec( |
| 423 | "DROP TABLE temp.dbx;" |
| 424 | "CREATE VIRTUAL TABLE temp.dbx USING dbstat(%s);" |
| @@ -441,11 +441,11 @@ | |
| 441 | ); |
| 442 | } |
| 443 | fsize = file_size(g.zLocalDbName); |
| 444 | approxSizeName(sizeof(zBuf), zBuf, fsize); |
| 445 | @ <h2>%h(file_tail(g.zLocalDbName)) Size: %s(zBuf)</h2> |
| 446 | @ <center><svg width='800' height='500'> |
| 447 | piechart_render(800,500,PIE_OTHER|PIE_PERCENT); |
| 448 | @ </svg></center> |
| 449 | } |
| 450 | style_footer(); |
| 451 | } |
| 452 |
| --- src/stat.c | |
| +++ src/stat.c | |
| @@ -412,13 +412,13 @@ | |
| 412 | ); |
| 413 | } |
| 414 | fsize = file_size(g.zRepositoryName); |
| 415 | approxSizeName(sizeof(zBuf), zBuf, fsize); |
| 416 | @ <h2>Repository Size: %s(zBuf)</h2> |
| 417 | @ <svg class="statistics-report-pie-chart" width='800' height='500'> |
| 418 | piechart_render(800,500,PIE_OTHER|PIE_PERCENT); |
| 419 | @ </svg> |
| 420 | |
| 421 | if( g.localOpen ){ |
| 422 | db_multi_exec( |
| 423 | "DROP TABLE temp.dbx;" |
| 424 | "CREATE VIRTUAL TABLE temp.dbx USING dbstat(%s);" |
| @@ -441,11 +441,11 @@ | |
| 441 | ); |
| 442 | } |
| 443 | fsize = file_size(g.zLocalDbName); |
| 444 | approxSizeName(sizeof(zBuf), zBuf, fsize); |
| 445 | @ <h2>%h(file_tail(g.zLocalDbName)) Size: %s(zBuf)</h2> |
| 446 | @ <svg class="statistics-report-pie-chart" width='800' height='500'> |
| 447 | piechart_render(800,500,PIE_OTHER|PIE_PERCENT); |
| 448 | @ </svg> |
| 449 | } |
| 450 | style_footer(); |
| 451 | } |
| 452 |
+6
-4
| --- src/statrep.c | ||
| +++ src/statrep.c | ||
| @@ -339,13 +339,14 @@ | ||
| 339 | 339 | "CREATE TEMP TABLE piechart(amt,label);" |
| 340 | 340 | "INSERT INTO piechart SELECT count(*), ifnull(euser,user) FROM v_reports" |
| 341 | 341 | " GROUP BY ifnull(euser,user) ORDER BY count(*) DESC;" |
| 342 | 342 | ); |
| 343 | 343 | if( db_int(0, "SELECT count(*) FROM piechart")>=2 ){ |
| 344 | - @ <center><svg width=700 height=400> | |
| 344 | + @ <svg class="statistics-report-pie-chart" width=700 height=400> | |
| 345 | 345 | piechart_render(700, 400, PIE_OTHER|PIE_PERCENT); |
| 346 | - @ </svg></centre><hr/> | |
| 346 | + @ </svg> | |
| 347 | + @ <hr/> | |
| 347 | 348 | } |
| 348 | 349 | @ <table class='statistics-report-table-events' border='0' |
| 349 | 350 | @ cellpadding='2' cellspacing='0' id='statsTable'> |
| 350 | 351 | @ <thead><tr> |
| 351 | 352 | @ <th>User</th> |
| @@ -498,13 +499,14 @@ | ||
| 498 | 499 | " WHEN 5 THEN 'Friday'" |
| 499 | 500 | " WHEN 6 THEN 'Saturday'" |
| 500 | 501 | " ELSE 'ERROR' END;", zUserName |
| 501 | 502 | ); |
| 502 | 503 | if( db_int(0, "SELECT count(*) FROM piechart")>=2 ){ |
| 503 | - @ <center><svg width=700 height=400> | |
| 504 | + @ <svg class="statistics-report-pie-chart" width=700 height=400> | |
| 504 | 505 | piechart_render(700, 400, PIE_OTHER|PIE_PERCENT); |
| 505 | - @ </svg></centre><hr/> | |
| 506 | + @ </svg> | |
| 507 | + @ <hr/> | |
| 506 | 508 | } |
| 507 | 509 | @ <table class='statistics-report-table-events' border='0' |
| 508 | 510 | @ cellpadding='2' cellspacing='0' id='statsTable'> |
| 509 | 511 | @ <thead><tr> |
| 510 | 512 | @ <th>DoW</th> |
| 511 | 513 |
| --- src/statrep.c | |
| +++ src/statrep.c | |
| @@ -339,13 +339,14 @@ | |
| 339 | "CREATE TEMP TABLE piechart(amt,label);" |
| 340 | "INSERT INTO piechart SELECT count(*), ifnull(euser,user) FROM v_reports" |
| 341 | " GROUP BY ifnull(euser,user) ORDER BY count(*) DESC;" |
| 342 | ); |
| 343 | if( db_int(0, "SELECT count(*) FROM piechart")>=2 ){ |
| 344 | @ <center><svg width=700 height=400> |
| 345 | piechart_render(700, 400, PIE_OTHER|PIE_PERCENT); |
| 346 | @ </svg></centre><hr/> |
| 347 | } |
| 348 | @ <table class='statistics-report-table-events' border='0' |
| 349 | @ cellpadding='2' cellspacing='0' id='statsTable'> |
| 350 | @ <thead><tr> |
| 351 | @ <th>User</th> |
| @@ -498,13 +499,14 @@ | |
| 498 | " WHEN 5 THEN 'Friday'" |
| 499 | " WHEN 6 THEN 'Saturday'" |
| 500 | " ELSE 'ERROR' END;", zUserName |
| 501 | ); |
| 502 | if( db_int(0, "SELECT count(*) FROM piechart")>=2 ){ |
| 503 | @ <center><svg width=700 height=400> |
| 504 | piechart_render(700, 400, PIE_OTHER|PIE_PERCENT); |
| 505 | @ </svg></centre><hr/> |
| 506 | } |
| 507 | @ <table class='statistics-report-table-events' border='0' |
| 508 | @ cellpadding='2' cellspacing='0' id='statsTable'> |
| 509 | @ <thead><tr> |
| 510 | @ <th>DoW</th> |
| 511 |
| --- src/statrep.c | |
| +++ src/statrep.c | |
| @@ -339,13 +339,14 @@ | |
| 339 | "CREATE TEMP TABLE piechart(amt,label);" |
| 340 | "INSERT INTO piechart SELECT count(*), ifnull(euser,user) FROM v_reports" |
| 341 | " GROUP BY ifnull(euser,user) ORDER BY count(*) DESC;" |
| 342 | ); |
| 343 | if( db_int(0, "SELECT count(*) FROM piechart")>=2 ){ |
| 344 | @ <svg class="statistics-report-pie-chart" width=700 height=400> |
| 345 | piechart_render(700, 400, PIE_OTHER|PIE_PERCENT); |
| 346 | @ </svg> |
| 347 | @ <hr/> |
| 348 | } |
| 349 | @ <table class='statistics-report-table-events' border='0' |
| 350 | @ cellpadding='2' cellspacing='0' id='statsTable'> |
| 351 | @ <thead><tr> |
| 352 | @ <th>User</th> |
| @@ -498,13 +499,14 @@ | |
| 499 | " WHEN 5 THEN 'Friday'" |
| 500 | " WHEN 6 THEN 'Saturday'" |
| 501 | " ELSE 'ERROR' END;", zUserName |
| 502 | ); |
| 503 | if( db_int(0, "SELECT count(*) FROM piechart")>=2 ){ |
| 504 | @ <svg class="statistics-report-pie-chart" width=700 height=400> |
| 505 | piechart_render(700, 400, PIE_OTHER|PIE_PERCENT); |
| 506 | @ </svg> |
| 507 | @ <hr/> |
| 508 | } |
| 509 | @ <table class='statistics-report-table-events' border='0' |
| 510 | @ cellpadding='2' cellspacing='0' id='statsTable'> |
| 511 | @ <thead><tr> |
| 512 | @ <th>DoW</th> |
| 513 |
+10
| --- src/style.c | ||
| +++ src/style.c | ||
| @@ -1318,10 +1318,15 @@ | ||
| 1318 | 1318 | { "table.label-value th", |
| 1319 | 1319 | "The label/value pairs on (for example) the ci page", |
| 1320 | 1320 | @ vertical-align: top; |
| 1321 | 1321 | @ text-align: right; |
| 1322 | 1322 | @ padding: 0.2ex 2ex; |
| 1323 | + }, | |
| 1324 | + { ".statistics-report-pie-chart", | |
| 1325 | + "for the /reports pie chart", | |
| 1326 | + @ display: block; | |
| 1327 | + @ margin: auto; | |
| 1323 | 1328 | }, |
| 1324 | 1329 | { ".statistics-report-graph-line", |
| 1325 | 1330 | "for the /reports views", |
| 1326 | 1331 | @ background-color: #446979; |
| 1327 | 1332 | }, |
| @@ -1429,10 +1434,15 @@ | ||
| 1429 | 1434 | { "span.snippet>mark", |
| 1430 | 1435 | "Search markup", |
| 1431 | 1436 | @ background-color: inherit; |
| 1432 | 1437 | @ font-weight: bold; |
| 1433 | 1438 | }, |
| 1439 | + { ".search", | |
| 1440 | + "Search form", | |
| 1441 | + @ display: block; | |
| 1442 | + @ margin: auto; | |
| 1443 | + }, | |
| 1434 | 1444 | { "div.searchForm", |
| 1435 | 1445 | "Container for the search terms entry box", |
| 1436 | 1446 | @ text-align: center; |
| 1437 | 1447 | }, |
| 1438 | 1448 | { "p.searchEmpty", |
| 1439 | 1449 |
| --- src/style.c | |
| +++ src/style.c | |
| @@ -1318,10 +1318,15 @@ | |
| 1318 | { "table.label-value th", |
| 1319 | "The label/value pairs on (for example) the ci page", |
| 1320 | @ vertical-align: top; |
| 1321 | @ text-align: right; |
| 1322 | @ padding: 0.2ex 2ex; |
| 1323 | }, |
| 1324 | { ".statistics-report-graph-line", |
| 1325 | "for the /reports views", |
| 1326 | @ background-color: #446979; |
| 1327 | }, |
| @@ -1429,10 +1434,15 @@ | |
| 1429 | { "span.snippet>mark", |
| 1430 | "Search markup", |
| 1431 | @ background-color: inherit; |
| 1432 | @ font-weight: bold; |
| 1433 | }, |
| 1434 | { "div.searchForm", |
| 1435 | "Container for the search terms entry box", |
| 1436 | @ text-align: center; |
| 1437 | }, |
| 1438 | { "p.searchEmpty", |
| 1439 |
| --- src/style.c | |
| +++ src/style.c | |
| @@ -1318,10 +1318,15 @@ | |
| 1318 | { "table.label-value th", |
| 1319 | "The label/value pairs on (for example) the ci page", |
| 1320 | @ vertical-align: top; |
| 1321 | @ text-align: right; |
| 1322 | @ padding: 0.2ex 2ex; |
| 1323 | }, |
| 1324 | { ".statistics-report-pie-chart", |
| 1325 | "for the /reports pie chart", |
| 1326 | @ display: block; |
| 1327 | @ margin: auto; |
| 1328 | }, |
| 1329 | { ".statistics-report-graph-line", |
| 1330 | "for the /reports views", |
| 1331 | @ background-color: #446979; |
| 1332 | }, |
| @@ -1429,10 +1434,15 @@ | |
| 1434 | { "span.snippet>mark", |
| 1435 | "Search markup", |
| 1436 | @ background-color: inherit; |
| 1437 | @ font-weight: bold; |
| 1438 | }, |
| 1439 | { ".search", |
| 1440 | "Search form", |
| 1441 | @ display: block; |
| 1442 | @ margin: auto; |
| 1443 | }, |
| 1444 | { "div.searchForm", |
| 1445 | "Container for the search terms entry box", |
| 1446 | @ text-align: center; |
| 1447 | }, |
| 1448 | { "p.searchEmpty", |
| 1449 |
+2
-2
| --- src/user.c | ||
| +++ src/user.c | ||
| @@ -472,11 +472,11 @@ | ||
| 472 | 472 | style_submenu_element("Newer", "Newer entries", |
| 473 | 473 | "%s/access_log?o=%d&n=%d&y=%d", g.zTop, skip>=n ? skip-n : 0, |
| 474 | 474 | n, y); |
| 475 | 475 | } |
| 476 | 476 | rc = db_prepare_ignore_error(&q, "%s", blob_sql_text(&sql)); |
| 477 | - @ <center><table border="1" cellpadding="5" id='logtable'> | |
| 477 | + @ <table border="1" cellpadding="5" id="logtable" align="center"> | |
| 478 | 478 | @ <thead><tr><th width="33%%">Date</th><th width="34%%">User</th> |
| 479 | 479 | @ <th width="33%%">IP Address</th></tr></thead><tbody> |
| 480 | 480 | while( rc==SQLITE_OK && db_step(&q)==SQLITE_ROW ){ |
| 481 | 481 | const char *zName = db_column_text(&q, 0); |
| 482 | 482 | const char *zIP = db_column_text(&q, 1); |
| @@ -497,11 +497,11 @@ | ||
| 497 | 497 | } |
| 498 | 498 | if( skip>0 || cnt>n ){ |
| 499 | 499 | style_submenu_element("All", "All entries", |
| 500 | 500 | "%s/access_log?n=10000000", g.zTop); |
| 501 | 501 | } |
| 502 | - @ </tbody></table></center> | |
| 502 | + @ </tbody></table> | |
| 503 | 503 | db_finalize(&q); |
| 504 | 504 | @ <hr> |
| 505 | 505 | @ <form method="post" action="%s(g.zTop)/access_log"> |
| 506 | 506 | @ <label><input type="checkbox" name="delold"> |
| 507 | 507 | @ Delete all but the most recent 200 entries</input></label> |
| 508 | 508 |
| --- src/user.c | |
| +++ src/user.c | |
| @@ -472,11 +472,11 @@ | |
| 472 | style_submenu_element("Newer", "Newer entries", |
| 473 | "%s/access_log?o=%d&n=%d&y=%d", g.zTop, skip>=n ? skip-n : 0, |
| 474 | n, y); |
| 475 | } |
| 476 | rc = db_prepare_ignore_error(&q, "%s", blob_sql_text(&sql)); |
| 477 | @ <center><table border="1" cellpadding="5" id='logtable'> |
| 478 | @ <thead><tr><th width="33%%">Date</th><th width="34%%">User</th> |
| 479 | @ <th width="33%%">IP Address</th></tr></thead><tbody> |
| 480 | while( rc==SQLITE_OK && db_step(&q)==SQLITE_ROW ){ |
| 481 | const char *zName = db_column_text(&q, 0); |
| 482 | const char *zIP = db_column_text(&q, 1); |
| @@ -497,11 +497,11 @@ | |
| 497 | } |
| 498 | if( skip>0 || cnt>n ){ |
| 499 | style_submenu_element("All", "All entries", |
| 500 | "%s/access_log?n=10000000", g.zTop); |
| 501 | } |
| 502 | @ </tbody></table></center> |
| 503 | db_finalize(&q); |
| 504 | @ <hr> |
| 505 | @ <form method="post" action="%s(g.zTop)/access_log"> |
| 506 | @ <label><input type="checkbox" name="delold"> |
| 507 | @ Delete all but the most recent 200 entries</input></label> |
| 508 |
| --- src/user.c | |
| +++ src/user.c | |
| @@ -472,11 +472,11 @@ | |
| 472 | style_submenu_element("Newer", "Newer entries", |
| 473 | "%s/access_log?o=%d&n=%d&y=%d", g.zTop, skip>=n ? skip-n : 0, |
| 474 | n, y); |
| 475 | } |
| 476 | rc = db_prepare_ignore_error(&q, "%s", blob_sql_text(&sql)); |
| 477 | @ <table border="1" cellpadding="5" id="logtable" align="center"> |
| 478 | @ <thead><tr><th width="33%%">Date</th><th width="34%%">User</th> |
| 479 | @ <th width="33%%">IP Address</th></tr></thead><tbody> |
| 480 | while( rc==SQLITE_OK && db_step(&q)==SQLITE_ROW ){ |
| 481 | const char *zName = db_column_text(&q, 0); |
| 482 | const char *zIP = db_column_text(&q, 1); |
| @@ -497,11 +497,11 @@ | |
| 497 | } |
| 498 | if( skip>0 || cnt>n ){ |
| 499 | style_submenu_element("All", "All entries", |
| 500 | "%s/access_log?n=10000000", g.zTop); |
| 501 | } |
| 502 | @ </tbody></table> |
| 503 | db_finalize(&q); |
| 504 | @ <hr> |
| 505 | @ <form method="post" action="%s(g.zTop)/access_log"> |
| 506 | @ <label><input type="checkbox" name="delold"> |
| 507 | @ Delete all but the most recent 200 entries</input></label> |
| 508 |
+1
-1
| --- src/wikiformat.c | ||
| +++ src/wikiformat.c | ||
| @@ -1996,11 +1996,11 @@ | ||
| 1996 | 1996 | ** Attempt to reformat messy HTML to be easily readable by humans. |
| 1997 | 1997 | ** |
| 1998 | 1998 | ** * Try to keep lines less than 80 characters in length |
| 1999 | 1999 | ** * Collapse white space into a single space |
| 2000 | 2000 | ** * Put a blank line before: |
| 2001 | -** <blockquote><center><code><hN><p><pre><table> | |
| 2001 | +** <blockquote><code><hN><p><pre><table> | |
| 2002 | 2002 | ** * Put a newline after <br> and <hr> |
| 2003 | 2003 | ** * Start each of the following elements on a new line: |
| 2004 | 2004 | ** <address><cite><dd><div><dl><dt><li><ol><samp> |
| 2005 | 2005 | ** <tbody><td><tfoot><th><thead><tr><ul> |
| 2006 | 2006 | ** |
| 2007 | 2007 |
| --- src/wikiformat.c | |
| +++ src/wikiformat.c | |
| @@ -1996,11 +1996,11 @@ | |
| 1996 | ** Attempt to reformat messy HTML to be easily readable by humans. |
| 1997 | ** |
| 1998 | ** * Try to keep lines less than 80 characters in length |
| 1999 | ** * Collapse white space into a single space |
| 2000 | ** * Put a blank line before: |
| 2001 | ** <blockquote><center><code><hN><p><pre><table> |
| 2002 | ** * Put a newline after <br> and <hr> |
| 2003 | ** * Start each of the following elements on a new line: |
| 2004 | ** <address><cite><dd><div><dl><dt><li><ol><samp> |
| 2005 | ** <tbody><td><tfoot><th><thead><tr><ul> |
| 2006 | ** |
| 2007 |
| --- src/wikiformat.c | |
| +++ src/wikiformat.c | |
| @@ -1996,11 +1996,11 @@ | |
| 1996 | ** Attempt to reformat messy HTML to be easily readable by humans. |
| 1997 | ** |
| 1998 | ** * Try to keep lines less than 80 characters in length |
| 1999 | ** * Collapse white space into a single space |
| 2000 | ** * Put a blank line before: |
| 2001 | ** <blockquote><code><hN><p><pre><table> |
| 2002 | ** * Put a newline after <br> and <hr> |
| 2003 | ** * Start each of the following elements on a new line: |
| 2004 | ** <address><cite><dd><div><dl><dt><li><ol><samp> |
| 2005 | ** <tbody><td><tfoot><th><thead><tr><ul> |
| 2006 | ** |
| 2007 |
+11
-10
| --- www/branching.wiki | ||
| +++ www/branching.wiki | ||
| @@ -1,16 +1,17 @@ | ||
| 1 | 1 | <title>Branching, Forking, Merging, and Tagging</title> |
| 2 | +<style>table { margin: auto }</style> | |
| 2 | 3 | <h2>Background</h2> |
| 3 | 4 | |
| 4 | 5 | In a simple and perfect world, the development of a project would proceed |
| 5 | 6 | linearly, as shown in figure 1. |
| 6 | 7 | |
| 7 | -<center><table border=1 cellpadding=10 hspace=10 vspace=10> | |
| 8 | +<table border=1 cellpadding=10 hspace=10 vspace=10> | |
| 8 | 9 | <tr><td align="center"> |
| 9 | 10 | <img src="branch01.gif" width=280 height=68><br> |
| 10 | 11 | Figure 1 |
| 11 | -</td></tr></table></center> | |
| 12 | +</td></tr></table> | |
| 12 | 13 | |
| 13 | 14 | Each circle represents a check-in. For the sake of clarity, the check-ins |
| 14 | 15 | are given small consecutive numbers. In a real system, of course, the |
| 15 | 16 | check-in numbers would be 40-character SHA1 hashes since it is not possible |
| 16 | 17 | to allocate collision-free sequential numbers in a distributed system. |
| @@ -38,15 +39,15 @@ | ||
| 38 | 39 | |
| 39 | 40 | Alas, reality often interferes with the simple linear development of a |
| 40 | 41 | project. Suppose two programmers make independent modifications to check-in 2. |
| 41 | 42 | After both changes are committed, the check-in graph looks like figure 2: |
| 42 | 43 | |
| 43 | -<center><table border=1 cellpadding=10 hspace=10 vspace=10> | |
| 44 | +<table border=1 cellpadding=10 hspace=10 vspace=10> | |
| 44 | 45 | <tr><td align="center"> |
| 45 | 46 | <img src="branch02.gif" width=210 height=140><br> |
| 46 | 47 | Figure 2 |
| 47 | -</td></tr></table></center> | |
| 48 | +</td></tr></table> | |
| 48 | 49 | |
| 49 | 50 | The graph in figure 2 has two leaves: check-ins 3 and 4. Check-in 2 has |
| 50 | 51 | two children, check-ins 3 and 4. We call this state a <i>fork</i>. |
| 51 | 52 | |
| 52 | 53 | Fossil tries to prevent forks. Suppose two programmers named Alice and |
| @@ -77,15 +78,15 @@ | ||
| 77 | 78 | To resolve this situation, Alice can use the fossil <b>merge</b> command |
| 78 | 79 | to merge in Bob's changes in her local copy of check-in 3. Then she |
| 79 | 80 | can commit the results as check-in 5. This results in a DAG as shown |
| 80 | 81 | in figure 3. |
| 81 | 82 | |
| 82 | -<center><table border=1 cellpadding=10 hspace=10 vspace=10> | |
| 83 | +<table border=1 cellpadding=10 hspace=10 vspace=10> | |
| 83 | 84 | <tr><td align="center"> |
| 84 | 85 | <img src="branch03.gif" width=282 height=152><br> |
| 85 | 86 | Figure 3 |
| 86 | -</td></tr></table></center> | |
| 87 | +</td></tr></table> | |
| 87 | 88 | |
| 88 | 89 | Check-in 5 is a child of check-in 3 because it was created by editing |
| 89 | 90 | check-in 3. But check-in 5 also inherits the changes from check-in 4 by |
| 90 | 91 | virtue of the merge. So we say that check-in 5 is a <i>merge child</i> |
| 91 | 92 | of check-in 4 and that it is a <i>direct child</i> of check-in 3. |
| @@ -124,15 +125,15 @@ | ||
| 124 | 125 | When multiple leaves are desirable, we call this <i>branching</i> |
| 125 | 126 | instead of <i>forking</i>. |
| 126 | 127 | Figure 4 shows an example of a project where there are two branches, one |
| 127 | 128 | for development work and another for testing. |
| 128 | 129 | |
| 129 | -<center><table border=1 cellpadding=10 hspace=10 vspace=10> | |
| 130 | +<table border=1 cellpadding=10 hspace=10 vspace=10> | |
| 130 | 131 | <tr><td align="center"> |
| 131 | 132 | <img src="branch04.gif" width=426 height=123><br> |
| 132 | 133 | Figure 4 |
| 133 | -</td></tr></table></center> | |
| 134 | +</td></tr></table> | |
| 134 | 135 | |
| 135 | 136 | The hypothetical scenario of figure 4 is this: The project starts and |
| 136 | 137 | progresses to a point where (at check-in 2) |
| 137 | 138 | it is ready to enter testing for its first release. |
| 138 | 139 | In a real project, of course, there might be hundreds or thousands of |
| @@ -164,15 +165,15 @@ | ||
| 164 | 165 | |
| 165 | 166 | Tags and properties are used in fossil to help express the intent, and |
| 166 | 167 | thus to distinguish between forks and branches. Figure 5 shows the |
| 167 | 168 | same scenario as figure 4 but with tags and properties added: |
| 168 | 169 | |
| 169 | -<center><table border=1 cellpadding=10 hspace=10 vspace=10> | |
| 170 | +<table border=1 cellpadding=10 hspace=10 vspace=10> | |
| 170 | 171 | <tr><td align="center"> |
| 171 | 172 | <img src="branch05.gif" width=485 height=177><br> |
| 172 | 173 | Figure 5 |
| 173 | -</td></tr></table></center> | |
| 174 | +</td></tr></table> | |
| 174 | 175 | |
| 175 | 176 | A <i>tag</i> is a name that is attached to a check-in. A |
| 176 | 177 | <i>property</i> is a name/value pair. Internally, fossil implements |
| 177 | 178 | tags as properties with a NULL value. So, tags and properties really |
| 178 | 179 | are much the same thing, and henceforth we will use the word "tag" |
| 179 | 180 |
| --- www/branching.wiki | |
| +++ www/branching.wiki | |
| @@ -1,16 +1,17 @@ | |
| 1 | <title>Branching, Forking, Merging, and Tagging</title> |
| 2 | <h2>Background</h2> |
| 3 | |
| 4 | In a simple and perfect world, the development of a project would proceed |
| 5 | linearly, as shown in figure 1. |
| 6 | |
| 7 | <center><table border=1 cellpadding=10 hspace=10 vspace=10> |
| 8 | <tr><td align="center"> |
| 9 | <img src="branch01.gif" width=280 height=68><br> |
| 10 | Figure 1 |
| 11 | </td></tr></table></center> |
| 12 | |
| 13 | Each circle represents a check-in. For the sake of clarity, the check-ins |
| 14 | are given small consecutive numbers. In a real system, of course, the |
| 15 | check-in numbers would be 40-character SHA1 hashes since it is not possible |
| 16 | to allocate collision-free sequential numbers in a distributed system. |
| @@ -38,15 +39,15 @@ | |
| 38 | |
| 39 | Alas, reality often interferes with the simple linear development of a |
| 40 | project. Suppose two programmers make independent modifications to check-in 2. |
| 41 | After both changes are committed, the check-in graph looks like figure 2: |
| 42 | |
| 43 | <center><table border=1 cellpadding=10 hspace=10 vspace=10> |
| 44 | <tr><td align="center"> |
| 45 | <img src="branch02.gif" width=210 height=140><br> |
| 46 | Figure 2 |
| 47 | </td></tr></table></center> |
| 48 | |
| 49 | The graph in figure 2 has two leaves: check-ins 3 and 4. Check-in 2 has |
| 50 | two children, check-ins 3 and 4. We call this state a <i>fork</i>. |
| 51 | |
| 52 | Fossil tries to prevent forks. Suppose two programmers named Alice and |
| @@ -77,15 +78,15 @@ | |
| 77 | To resolve this situation, Alice can use the fossil <b>merge</b> command |
| 78 | to merge in Bob's changes in her local copy of check-in 3. Then she |
| 79 | can commit the results as check-in 5. This results in a DAG as shown |
| 80 | in figure 3. |
| 81 | |
| 82 | <center><table border=1 cellpadding=10 hspace=10 vspace=10> |
| 83 | <tr><td align="center"> |
| 84 | <img src="branch03.gif" width=282 height=152><br> |
| 85 | Figure 3 |
| 86 | </td></tr></table></center> |
| 87 | |
| 88 | Check-in 5 is a child of check-in 3 because it was created by editing |
| 89 | check-in 3. But check-in 5 also inherits the changes from check-in 4 by |
| 90 | virtue of the merge. So we say that check-in 5 is a <i>merge child</i> |
| 91 | of check-in 4 and that it is a <i>direct child</i> of check-in 3. |
| @@ -124,15 +125,15 @@ | |
| 124 | When multiple leaves are desirable, we call this <i>branching</i> |
| 125 | instead of <i>forking</i>. |
| 126 | Figure 4 shows an example of a project where there are two branches, one |
| 127 | for development work and another for testing. |
| 128 | |
| 129 | <center><table border=1 cellpadding=10 hspace=10 vspace=10> |
| 130 | <tr><td align="center"> |
| 131 | <img src="branch04.gif" width=426 height=123><br> |
| 132 | Figure 4 |
| 133 | </td></tr></table></center> |
| 134 | |
| 135 | The hypothetical scenario of figure 4 is this: The project starts and |
| 136 | progresses to a point where (at check-in 2) |
| 137 | it is ready to enter testing for its first release. |
| 138 | In a real project, of course, there might be hundreds or thousands of |
| @@ -164,15 +165,15 @@ | |
| 164 | |
| 165 | Tags and properties are used in fossil to help express the intent, and |
| 166 | thus to distinguish between forks and branches. Figure 5 shows the |
| 167 | same scenario as figure 4 but with tags and properties added: |
| 168 | |
| 169 | <center><table border=1 cellpadding=10 hspace=10 vspace=10> |
| 170 | <tr><td align="center"> |
| 171 | <img src="branch05.gif" width=485 height=177><br> |
| 172 | Figure 5 |
| 173 | </td></tr></table></center> |
| 174 | |
| 175 | A <i>tag</i> is a name that is attached to a check-in. A |
| 176 | <i>property</i> is a name/value pair. Internally, fossil implements |
| 177 | tags as properties with a NULL value. So, tags and properties really |
| 178 | are much the same thing, and henceforth we will use the word "tag" |
| 179 |
| --- www/branching.wiki | |
| +++ www/branching.wiki | |
| @@ -1,16 +1,17 @@ | |
| 1 | <title>Branching, Forking, Merging, and Tagging</title> |
| 2 | <style>table { margin: auto }</style> |
| 3 | <h2>Background</h2> |
| 4 | |
| 5 | In a simple and perfect world, the development of a project would proceed |
| 6 | linearly, as shown in figure 1. |
| 7 | |
| 8 | <table border=1 cellpadding=10 hspace=10 vspace=10> |
| 9 | <tr><td align="center"> |
| 10 | <img src="branch01.gif" width=280 height=68><br> |
| 11 | Figure 1 |
| 12 | </td></tr></table> |
| 13 | |
| 14 | Each circle represents a check-in. For the sake of clarity, the check-ins |
| 15 | are given small consecutive numbers. In a real system, of course, the |
| 16 | check-in numbers would be 40-character SHA1 hashes since it is not possible |
| 17 | to allocate collision-free sequential numbers in a distributed system. |
| @@ -38,15 +39,15 @@ | |
| 39 | |
| 40 | Alas, reality often interferes with the simple linear development of a |
| 41 | project. Suppose two programmers make independent modifications to check-in 2. |
| 42 | After both changes are committed, the check-in graph looks like figure 2: |
| 43 | |
| 44 | <table border=1 cellpadding=10 hspace=10 vspace=10> |
| 45 | <tr><td align="center"> |
| 46 | <img src="branch02.gif" width=210 height=140><br> |
| 47 | Figure 2 |
| 48 | </td></tr></table> |
| 49 | |
| 50 | The graph in figure 2 has two leaves: check-ins 3 and 4. Check-in 2 has |
| 51 | two children, check-ins 3 and 4. We call this state a <i>fork</i>. |
| 52 | |
| 53 | Fossil tries to prevent forks. Suppose two programmers named Alice and |
| @@ -77,15 +78,15 @@ | |
| 78 | To resolve this situation, Alice can use the fossil <b>merge</b> command |
| 79 | to merge in Bob's changes in her local copy of check-in 3. Then she |
| 80 | can commit the results as check-in 5. This results in a DAG as shown |
| 81 | in figure 3. |
| 82 | |
| 83 | <table border=1 cellpadding=10 hspace=10 vspace=10> |
| 84 | <tr><td align="center"> |
| 85 | <img src="branch03.gif" width=282 height=152><br> |
| 86 | Figure 3 |
| 87 | </td></tr></table> |
| 88 | |
| 89 | Check-in 5 is a child of check-in 3 because it was created by editing |
| 90 | check-in 3. But check-in 5 also inherits the changes from check-in 4 by |
| 91 | virtue of the merge. So we say that check-in 5 is a <i>merge child</i> |
| 92 | of check-in 4 and that it is a <i>direct child</i> of check-in 3. |
| @@ -124,15 +125,15 @@ | |
| 125 | When multiple leaves are desirable, we call this <i>branching</i> |
| 126 | instead of <i>forking</i>. |
| 127 | Figure 4 shows an example of a project where there are two branches, one |
| 128 | for development work and another for testing. |
| 129 | |
| 130 | <table border=1 cellpadding=10 hspace=10 vspace=10> |
| 131 | <tr><td align="center"> |
| 132 | <img src="branch04.gif" width=426 height=123><br> |
| 133 | Figure 4 |
| 134 | </td></tr></table> |
| 135 | |
| 136 | The hypothetical scenario of figure 4 is this: The project starts and |
| 137 | progresses to a point where (at check-in 2) |
| 138 | it is ready to enter testing for its first release. |
| 139 | In a real project, of course, there might be hundreds or thousands of |
| @@ -164,15 +165,15 @@ | |
| 165 | |
| 166 | Tags and properties are used in fossil to help express the intent, and |
| 167 | thus to distinguish between forks and branches. Figure 5 shows the |
| 168 | same scenario as figure 4 but with tags and properties added: |
| 169 | |
| 170 | <table border=1 cellpadding=10 hspace=10 vspace=10> |
| 171 | <tr><td align="center"> |
| 172 | <img src="branch05.gif" width=485 height=177><br> |
| 173 | Figure 5 |
| 174 | </td></tr></table> |
| 175 | |
| 176 | A <i>tag</i> is a name that is attached to a check-in. A |
| 177 | <i>property</i> is a name/value pair. Internally, fossil implements |
| 178 | tags as properties with a NULL value. So, tags and properties really |
| 179 | are much the same thing, and henceforth we will use the word "tag" |
| 180 |
+1
-3
| --- www/copyright-release.html | ||
| +++ www/copyright-release.html | ||
| @@ -74,12 +74,11 @@ | ||
| 74 | 74 | |
| 75 | 75 | <p>By filling in the following information and signing your name, |
| 76 | 76 | you agree to be bound by all of the terms |
| 77 | 77 | set forth in this agreement. Please print clearly.</p> |
| 78 | 78 | |
| 79 | -<center> | |
| 80 | -<p><table width="80%" border="1" cellpadding="0" cellspacing="0"> | |
| 79 | +<table width="80%" border="1" cellpadding="0" cellspacing="0" align="center"> | |
| 81 | 80 | <tr><td width="20%" valign="top">Your name & email:</td><td width="80%"> |
| 82 | 81 | |
| 83 | 82 | <!-- Replace this line with your name and email --> <p> |
| 84 | 83 | |
| 85 | 84 | </td></tr> |
| @@ -95,14 +94,13 @@ | ||
| 95 | 94 | |
| 96 | 95 | </td></tr> |
| 97 | 96 | <tr><td valign="top">Signature:</td><td> <p> </td></tr> |
| 98 | 97 | <tr><td valign="top">Date:</td><td> <p> </td></tr> |
| 99 | 98 | </table> |
| 100 | -</center> | |
| 101 | 99 | |
| 102 | 100 | <p>Send completed forms to: |
| 103 | 101 | <blockquote> |
| 104 | 102 | Hipp, Wyrick & Company, Inc.<br> |
| 105 | 103 | 6200 Maple Cove Lane<br> |
| 106 | 104 | Charlotte, NC 28269-1086<br> |
| 107 | 105 | USA |
| 108 | 106 | </p> |
| 109 | 107 |
| --- www/copyright-release.html | |
| +++ www/copyright-release.html | |
| @@ -74,12 +74,11 @@ | |
| 74 | |
| 75 | <p>By filling in the following information and signing your name, |
| 76 | you agree to be bound by all of the terms |
| 77 | set forth in this agreement. Please print clearly.</p> |
| 78 | |
| 79 | <center> |
| 80 | <p><table width="80%" border="1" cellpadding="0" cellspacing="0"> |
| 81 | <tr><td width="20%" valign="top">Your name & email:</td><td width="80%"> |
| 82 | |
| 83 | <!-- Replace this line with your name and email --> <p> |
| 84 | |
| 85 | </td></tr> |
| @@ -95,14 +94,13 @@ | |
| 95 | |
| 96 | </td></tr> |
| 97 | <tr><td valign="top">Signature:</td><td> <p> </td></tr> |
| 98 | <tr><td valign="top">Date:</td><td> <p> </td></tr> |
| 99 | </table> |
| 100 | </center> |
| 101 | |
| 102 | <p>Send completed forms to: |
| 103 | <blockquote> |
| 104 | Hipp, Wyrick & Company, Inc.<br> |
| 105 | 6200 Maple Cove Lane<br> |
| 106 | Charlotte, NC 28269-1086<br> |
| 107 | USA |
| 108 | </p> |
| 109 |
| --- www/copyright-release.html | |
| +++ www/copyright-release.html | |
| @@ -74,12 +74,11 @@ | |
| 74 | |
| 75 | <p>By filling in the following information and signing your name, |
| 76 | you agree to be bound by all of the terms |
| 77 | set forth in this agreement. Please print clearly.</p> |
| 78 | |
| 79 | <table width="80%" border="1" cellpadding="0" cellspacing="0" align="center"> |
| 80 | <tr><td width="20%" valign="top">Your name & email:</td><td width="80%"> |
| 81 | |
| 82 | <!-- Replace this line with your name and email --> <p> |
| 83 | |
| 84 | </td></tr> |
| @@ -95,14 +94,13 @@ | |
| 94 | |
| 95 | </td></tr> |
| 96 | <tr><td valign="top">Signature:</td><td> <p> </td></tr> |
| 97 | <tr><td valign="top">Date:</td><td> <p> </td></tr> |
| 98 | </table> |
| 99 | |
| 100 | <p>Send completed forms to: |
| 101 | <blockquote> |
| 102 | Hipp, Wyrick & Company, Inc.<br> |
| 103 | 6200 Maple Cove Lane<br> |
| 104 | Charlotte, NC 28269-1086<br> |
| 105 | USA |
| 106 | </p> |
| 107 |
+2
-2
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -14,11 +14,11 @@ | ||
| 14 | 14 | might be biased in favor of Fossil. Ask around with people who have |
| 15 | 15 | used both Fossil and Git for other opinions. |
| 16 | 16 | |
| 17 | 17 | <h2>2.0 Executive Summary:</h2> |
| 18 | 18 | |
| 19 | -<blockquote><center><table border=1 cellpadding=5> | |
| 19 | +<blockquote><table border=1 cellpadding=5 align=center> | |
| 20 | 20 | <tr><th width="50%">GIT</th><th width="50%">FOSSIL</th></tr> |
| 21 | 21 | <tr><td>File versioning only</td> |
| 22 | 22 | <td>Versioning, Tickets, Wiki, and Technotes</td></tr> |
| 23 | 23 | <tr><td>Sharding</td><td>Replicating</td></tr> |
| 24 | 24 | <tr><td>Developer branches</td><td>Feature branches</td></tr> |
| @@ -29,11 +29,11 @@ | ||
| 29 | 29 | <td>Single-file relational database</td></tr> |
| 30 | 30 | <tr><td>One check-out per repository</td> |
| 31 | 31 | <td>Many check-outs per repository</td></tr> |
| 32 | 32 | <tr><td>Uses "<tt>rebase</tt>"</td><td>Immutable</td></tr> |
| 33 | 33 | <tr><td>GPL</td><td>BSD</td></tr> |
| 34 | -</table></center></blockquote> | |
| 34 | +</table></blockquote> | |
| 35 | 35 | |
| 36 | 36 | <h2>3.0 Discussion</h2> |
| 37 | 37 | |
| 38 | 38 | <h3>3.1 Feature Set</h3> |
| 39 | 39 | |
| 40 | 40 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -14,11 +14,11 @@ | |
| 14 | might be biased in favor of Fossil. Ask around with people who have |
| 15 | used both Fossil and Git for other opinions. |
| 16 | |
| 17 | <h2>2.0 Executive Summary:</h2> |
| 18 | |
| 19 | <blockquote><center><table border=1 cellpadding=5> |
| 20 | <tr><th width="50%">GIT</th><th width="50%">FOSSIL</th></tr> |
| 21 | <tr><td>File versioning only</td> |
| 22 | <td>Versioning, Tickets, Wiki, and Technotes</td></tr> |
| 23 | <tr><td>Sharding</td><td>Replicating</td></tr> |
| 24 | <tr><td>Developer branches</td><td>Feature branches</td></tr> |
| @@ -29,11 +29,11 @@ | |
| 29 | <td>Single-file relational database</td></tr> |
| 30 | <tr><td>One check-out per repository</td> |
| 31 | <td>Many check-outs per repository</td></tr> |
| 32 | <tr><td>Uses "<tt>rebase</tt>"</td><td>Immutable</td></tr> |
| 33 | <tr><td>GPL</td><td>BSD</td></tr> |
| 34 | </table></center></blockquote> |
| 35 | |
| 36 | <h2>3.0 Discussion</h2> |
| 37 | |
| 38 | <h3>3.1 Feature Set</h3> |
| 39 | |
| 40 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -14,11 +14,11 @@ | |
| 14 | might be biased in favor of Fossil. Ask around with people who have |
| 15 | used both Fossil and Git for other opinions. |
| 16 | |
| 17 | <h2>2.0 Executive Summary:</h2> |
| 18 | |
| 19 | <blockquote><table border=1 cellpadding=5 align=center> |
| 20 | <tr><th width="50%">GIT</th><th width="50%">FOSSIL</th></tr> |
| 21 | <tr><td>File versioning only</td> |
| 22 | <td>Versioning, Tickets, Wiki, and Technotes</td></tr> |
| 23 | <tr><td>Sharding</td><td>Replicating</td></tr> |
| 24 | <tr><td>Developer branches</td><td>Feature branches</td></tr> |
| @@ -29,11 +29,11 @@ | |
| 29 | <td>Single-file relational database</td></tr> |
| 30 | <tr><td>One check-out per repository</td> |
| 31 | <td>Many check-outs per repository</td></tr> |
| 32 | <tr><td>Uses "<tt>rebase</tt>"</td><td>Immutable</td></tr> |
| 33 | <tr><td>GPL</td><td>BSD</td></tr> |
| 34 | </table></blockquote> |
| 35 | |
| 36 | <h2>3.0 Discussion</h2> |
| 37 | |
| 38 | <h3>3.1 Feature Set</h3> |
| 39 | |
| 40 |
+1
-1
| --- www/index.wiki | ||
| +++ www/index.wiki | ||
| @@ -18,11 +18,11 @@ | ||
| 18 | 18 | <ul> |
| 19 | 19 | <li> [http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-users | sign-up] |
| 20 | 20 | <li> [http://www.mail-archive.com/[email protected] | archives] |
| 21 | 21 | </ul> |
| 22 | 22 | </ul> |
| 23 | -<center><img src="fossil3.gif"></center> | |
| 23 | +<img src="fossil3.gif" style="margin:auto"> | |
| 24 | 24 | </div> |
| 25 | 25 | |
| 26 | 26 | <p>Fossil is a simple, high-reliability, distributed software configuration |
| 27 | 27 | management system with these advanced features: |
| 28 | 28 | |
| 29 | 29 |
| --- www/index.wiki | |
| +++ www/index.wiki | |
| @@ -18,11 +18,11 @@ | |
| 18 | <ul> |
| 19 | <li> [http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-users | sign-up] |
| 20 | <li> [http://www.mail-archive.com/[email protected] | archives] |
| 21 | </ul> |
| 22 | </ul> |
| 23 | <center><img src="fossil3.gif"></center> |
| 24 | </div> |
| 25 | |
| 26 | <p>Fossil is a simple, high-reliability, distributed software configuration |
| 27 | management system with these advanced features: |
| 28 | |
| 29 |
| --- www/index.wiki | |
| +++ www/index.wiki | |
| @@ -18,11 +18,11 @@ | |
| 18 | <ul> |
| 19 | <li> [http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-users | sign-up] |
| 20 | <li> [http://www.mail-archive.com/[email protected] | archives] |
| 21 | </ul> |
| 22 | </ul> |
| 23 | <img src="fossil3.gif" style="margin:auto"> |
| 24 | </div> |
| 25 | |
| 26 | <p>Fossil is a simple, high-reliability, distributed software configuration |
| 27 | management system with these advanced features: |
| 28 | |
| 29 |
+7
-9
| --- www/mkdownload.tcl | ||
| +++ www/mkdownload.tcl | ||
| @@ -31,26 +31,24 @@ | ||
| 31 | 31 | <a href='/fossil/ticket'>Tickets</a> |
| 32 | 32 | <a href='/fossil/wiki'>Wiki</a> |
| 33 | 33 | <a href='/download.html' class='active'>Download</a> |
| 34 | 34 | </div> |
| 35 | 35 | <div class="content"> |
| 36 | -<p> | |
| 37 | - | |
| 38 | -<center><font size=4>} | |
| 36 | +<p style="font-size:1.2em; text-align:center">} | |
| 39 | 37 | puts $out \ |
| 40 | 38 | "<b>To install Fossil →</b> download the stand-alone executable" |
| 41 | 39 | puts $out \ |
| 42 | 40 | {and put it on your $PATH. |
| 43 | -</font><p><small> | |
| 41 | +</p> | |
| 42 | +<p style="text-align:center"> | |
| 44 | 43 | RPMs available |
| 45 | 44 | <a href="http://download.opensuse.org/repositories/home:/rmax:/fossil/"> |
| 46 | 45 | here.</a> |
| 47 | 46 | Cryptographic checksums for download files are |
| 48 | 47 | <a href="http://www.hwaci.com/fossil_download_checksums.html">here</a>. |
| 49 | -</small></p> | |
| 50 | -</center> | |
| 51 | - | |
| 48 | +</p> | |
| 49 | +<hr> | |
| 52 | 50 | <table cellpadding="10"> |
| 53 | 51 | } |
| 54 | 52 | |
| 55 | 53 | # Find all all unique timestamps. |
| 56 | 54 | # |
| @@ -62,12 +60,12 @@ | ||
| 62 | 60 | |
| 63 | 61 | # Do all versions from newest to oldest |
| 64 | 62 | # |
| 65 | 63 | foreach vers [lsort -decr -real [array names avers]] { |
| 66 | 64 | set hr "/fossil/timeline?c=version-$vers;y=ci" |
| 67 | - puts $out "<tr><td colspan=6 align=left><hr>" | |
| 68 | - puts $out "<center><b><a href=\"$hr\">Version $vers</a></b></center>" | |
| 65 | + puts $out "<tr><td colspan=6 align=center>" | |
| 66 | + puts $out "<b><a href=\"$hr\">Version $vers</a></b>" | |
| 69 | 67 | puts $out "</td></tr>" |
| 70 | 68 | puts $out "<tr>" |
| 71 | 69 | |
| 72 | 70 | foreach {prefix suffix img desc} { |
| 73 | 71 | fossil-linux-x86 zip linux.gif {Linux 3.x x86} |
| 74 | 72 |
| --- www/mkdownload.tcl | |
| +++ www/mkdownload.tcl | |
| @@ -31,26 +31,24 @@ | |
| 31 | <a href='/fossil/ticket'>Tickets</a> |
| 32 | <a href='/fossil/wiki'>Wiki</a> |
| 33 | <a href='/download.html' class='active'>Download</a> |
| 34 | </div> |
| 35 | <div class="content"> |
| 36 | <p> |
| 37 | |
| 38 | <center><font size=4>} |
| 39 | puts $out \ |
| 40 | "<b>To install Fossil →</b> download the stand-alone executable" |
| 41 | puts $out \ |
| 42 | {and put it on your $PATH. |
| 43 | </font><p><small> |
| 44 | RPMs available |
| 45 | <a href="http://download.opensuse.org/repositories/home:/rmax:/fossil/"> |
| 46 | here.</a> |
| 47 | Cryptographic checksums for download files are |
| 48 | <a href="http://www.hwaci.com/fossil_download_checksums.html">here</a>. |
| 49 | </small></p> |
| 50 | </center> |
| 51 | |
| 52 | <table cellpadding="10"> |
| 53 | } |
| 54 | |
| 55 | # Find all all unique timestamps. |
| 56 | # |
| @@ -62,12 +60,12 @@ | |
| 62 | |
| 63 | # Do all versions from newest to oldest |
| 64 | # |
| 65 | foreach vers [lsort -decr -real [array names avers]] { |
| 66 | set hr "/fossil/timeline?c=version-$vers;y=ci" |
| 67 | puts $out "<tr><td colspan=6 align=left><hr>" |
| 68 | puts $out "<center><b><a href=\"$hr\">Version $vers</a></b></center>" |
| 69 | puts $out "</td></tr>" |
| 70 | puts $out "<tr>" |
| 71 | |
| 72 | foreach {prefix suffix img desc} { |
| 73 | fossil-linux-x86 zip linux.gif {Linux 3.x x86} |
| 74 |
| --- www/mkdownload.tcl | |
| +++ www/mkdownload.tcl | |
| @@ -31,26 +31,24 @@ | |
| 31 | <a href='/fossil/ticket'>Tickets</a> |
| 32 | <a href='/fossil/wiki'>Wiki</a> |
| 33 | <a href='/download.html' class='active'>Download</a> |
| 34 | </div> |
| 35 | <div class="content"> |
| 36 | <p style="font-size:1.2em; text-align:center">} |
| 37 | puts $out \ |
| 38 | "<b>To install Fossil →</b> download the stand-alone executable" |
| 39 | puts $out \ |
| 40 | {and put it on your $PATH. |
| 41 | </p> |
| 42 | <p style="text-align:center"> |
| 43 | RPMs available |
| 44 | <a href="http://download.opensuse.org/repositories/home:/rmax:/fossil/"> |
| 45 | here.</a> |
| 46 | Cryptographic checksums for download files are |
| 47 | <a href="http://www.hwaci.com/fossil_download_checksums.html">here</a>. |
| 48 | </p> |
| 49 | <hr> |
| 50 | <table cellpadding="10"> |
| 51 | } |
| 52 | |
| 53 | # Find all all unique timestamps. |
| 54 | # |
| @@ -62,12 +60,12 @@ | |
| 60 | |
| 61 | # Do all versions from newest to oldest |
| 62 | # |
| 63 | foreach vers [lsort -decr -real [array names avers]] { |
| 64 | set hr "/fossil/timeline?c=version-$vers;y=ci" |
| 65 | puts $out "<tr><td colspan=6 align=center>" |
| 66 | puts $out "<b><a href=\"$hr\">Version $vers</a></b>" |
| 67 | puts $out "</td></tr>" |
| 68 | puts $out "<tr>" |
| 69 | |
| 70 | foreach {prefix suffix img desc} { |
| 71 | fossil-linux-x86 zip linux.gif {Linux 3.x x86} |
| 72 |
+1
-3
| --- www/mkindex.tcl | ||
| +++ www/mkindex.tcl | ||
| @@ -85,16 +85,14 @@ | ||
| 85 | 85 | set out [open permutedindex.html w] |
| 86 | 86 | fconfigure $out -encoding utf-8 -translation lf |
| 87 | 87 | puts $out \ |
| 88 | 88 | "<div class='fossil-doc' data-title='Index Of Fossil Documentation'>" |
| 89 | 89 | puts $out { |
| 90 | -<center> | |
| 91 | -<form action='../../../docsrch' method='GET'> | |
| 90 | +<form class="search" action='../../../docsrch' method='GET'> | |
| 92 | 91 | <input type="text" name="s" size="40" autofocus> |
| 93 | 92 | <input type="submit" value="Search Docs"> |
| 94 | 93 | </form> |
| 95 | -</center> | |
| 96 | 94 | <h2>Primary Documents:</h2> |
| 97 | 95 | <ul> |
| 98 | 96 | <li> <a href='quickstart.wiki'>Quick-start Guide</a> |
| 99 | 97 | <li> <a href='faq.wiki'>FAQ</a> |
| 100 | 98 | <li> <a href='build.wiki'>Compiling and installing Fossil</a> |
| 101 | 99 |
| --- www/mkindex.tcl | |
| +++ www/mkindex.tcl | |
| @@ -85,16 +85,14 @@ | |
| 85 | set out [open permutedindex.html w] |
| 86 | fconfigure $out -encoding utf-8 -translation lf |
| 87 | puts $out \ |
| 88 | "<div class='fossil-doc' data-title='Index Of Fossil Documentation'>" |
| 89 | puts $out { |
| 90 | <center> |
| 91 | <form action='../../../docsrch' method='GET'> |
| 92 | <input type="text" name="s" size="40" autofocus> |
| 93 | <input type="submit" value="Search Docs"> |
| 94 | </form> |
| 95 | </center> |
| 96 | <h2>Primary Documents:</h2> |
| 97 | <ul> |
| 98 | <li> <a href='quickstart.wiki'>Quick-start Guide</a> |
| 99 | <li> <a href='faq.wiki'>FAQ</a> |
| 100 | <li> <a href='build.wiki'>Compiling and installing Fossil</a> |
| 101 |
| --- www/mkindex.tcl | |
| +++ www/mkindex.tcl | |
| @@ -85,16 +85,14 @@ | |
| 85 | set out [open permutedindex.html w] |
| 86 | fconfigure $out -encoding utf-8 -translation lf |
| 87 | puts $out \ |
| 88 | "<div class='fossil-doc' data-title='Index Of Fossil Documentation'>" |
| 89 | puts $out { |
| 90 | <form class="search" action='../../../docsrch' method='GET'> |
| 91 | <input type="text" name="s" size="40" autofocus> |
| 92 | <input type="submit" value="Search Docs"> |
| 93 | </form> |
| 94 | <h2>Primary Documents:</h2> |
| 95 | <ul> |
| 96 | <li> <a href='quickstart.wiki'>Quick-start Guide</a> |
| 97 | <li> <a href='faq.wiki'>FAQ</a> |
| 98 | <li> <a href='build.wiki'>Compiling and installing Fossil</a> |
| 99 |
+1
-3
| --- www/permutedindex.html | ||
| +++ www/permutedindex.html | ||
| @@ -1,13 +1,11 @@ | ||
| 1 | 1 | <div class='fossil-doc' data-title='Index Of Fossil Documentation'> |
| 2 | 2 | |
| 3 | -<center> | |
| 4 | -<form action='../../../docsrch' method='GET'> | |
| 3 | +<form class="search" action='../../../docsrch' method='GET'> | |
| 5 | 4 | <input type="text" name="s" size="40" autofocus> |
| 6 | 5 | <input type="submit" value="Search Docs"> |
| 7 | 6 | </form> |
| 8 | -</center> | |
| 9 | 7 | <h2>Primary Documents:</h2> |
| 10 | 8 | <ul> |
| 11 | 9 | <li> <a href='quickstart.wiki'>Quick-start Guide</a> |
| 12 | 10 | <li> <a href='faq.wiki'>FAQ</a> |
| 13 | 11 | <li> <a href='build.wiki'>Compiling and installing Fossil</a> |
| 14 | 12 |
| --- www/permutedindex.html | |
| +++ www/permutedindex.html | |
| @@ -1,13 +1,11 @@ | |
| 1 | <div class='fossil-doc' data-title='Index Of Fossil Documentation'> |
| 2 | |
| 3 | <center> |
| 4 | <form action='../../../docsrch' method='GET'> |
| 5 | <input type="text" name="s" size="40" autofocus> |
| 6 | <input type="submit" value="Search Docs"> |
| 7 | </form> |
| 8 | </center> |
| 9 | <h2>Primary Documents:</h2> |
| 10 | <ul> |
| 11 | <li> <a href='quickstart.wiki'>Quick-start Guide</a> |
| 12 | <li> <a href='faq.wiki'>FAQ</a> |
| 13 | <li> <a href='build.wiki'>Compiling and installing Fossil</a> |
| 14 |
| --- www/permutedindex.html | |
| +++ www/permutedindex.html | |
| @@ -1,13 +1,11 @@ | |
| 1 | <div class='fossil-doc' data-title='Index Of Fossil Documentation'> |
| 2 | |
| 3 | <form class="search" action='../../../docsrch' method='GET'> |
| 4 | <input type="text" name="s" size="40" autofocus> |
| 5 | <input type="submit" value="Search Docs"> |
| 6 | </form> |
| 7 | <h2>Primary Documents:</h2> |
| 8 | <ul> |
| 9 | <li> <a href='quickstart.wiki'>Quick-start Guide</a> |
| 10 | <li> <a href='faq.wiki'>FAQ</a> |
| 11 | <li> <a href='build.wiki'>Compiling and installing Fossil</a> |
| 12 |
+2
-2
| --- www/sync.wiki | ||
| +++ www/sync.wiki | ||
| @@ -385,11 +385,11 @@ | ||
| 385 | 385 | </blockquote> |
| 386 | 386 | |
| 387 | 387 | <p>As of [/timeline?r=trunk&c=2015-03-19+03%3A57%3A46&n=20|2015-03-19], the configuration-name must be one of the |
| 388 | 388 | following values: |
| 389 | 389 | |
| 390 | -<center><table border=0> | |
| 390 | +<table border=0 align="center"> | |
| 391 | 391 | <tr><td valign="top"> |
| 392 | 392 | <ul> |
| 393 | 393 | <li> css |
| 394 | 394 | <li> header |
| 395 | 395 | <li> footer |
| @@ -436,11 +436,11 @@ | ||
| 436 | 436 | <li> @reportfmt |
| 437 | 437 | <li> @user |
| 438 | 438 | <li> @concealed |
| 439 | 439 | <li> @shun |
| 440 | 440 | </ul></td></tr> |
| 441 | -</table></center> | |
| 441 | +</table> | |
| 442 | 442 | |
| 443 | 443 | <p>New configuration-names are likely to be added in future releases of |
| 444 | 444 | Fossil. If the server receives a configuration-name that it does not |
| 445 | 445 | understand, the entire reqconfig card is silently ignored. The reqconfig |
| 446 | 446 | card might also be ignored if the user lacks sufficient privilege to |
| 447 | 447 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -385,11 +385,11 @@ | |
| 385 | </blockquote> |
| 386 | |
| 387 | <p>As of [/timeline?r=trunk&c=2015-03-19+03%3A57%3A46&n=20|2015-03-19], the configuration-name must be one of the |
| 388 | following values: |
| 389 | |
| 390 | <center><table border=0> |
| 391 | <tr><td valign="top"> |
| 392 | <ul> |
| 393 | <li> css |
| 394 | <li> header |
| 395 | <li> footer |
| @@ -436,11 +436,11 @@ | |
| 436 | <li> @reportfmt |
| 437 | <li> @user |
| 438 | <li> @concealed |
| 439 | <li> @shun |
| 440 | </ul></td></tr> |
| 441 | </table></center> |
| 442 | |
| 443 | <p>New configuration-names are likely to be added in future releases of |
| 444 | Fossil. If the server receives a configuration-name that it does not |
| 445 | understand, the entire reqconfig card is silently ignored. The reqconfig |
| 446 | card might also be ignored if the user lacks sufficient privilege to |
| 447 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -385,11 +385,11 @@ | |
| 385 | </blockquote> |
| 386 | |
| 387 | <p>As of [/timeline?r=trunk&c=2015-03-19+03%3A57%3A46&n=20|2015-03-19], the configuration-name must be one of the |
| 388 | following values: |
| 389 | |
| 390 | <table border=0 align="center"> |
| 391 | <tr><td valign="top"> |
| 392 | <ul> |
| 393 | <li> css |
| 394 | <li> header |
| 395 | <li> footer |
| @@ -436,11 +436,11 @@ | |
| 436 | <li> @reportfmt |
| 437 | <li> @user |
| 438 | <li> @concealed |
| 439 | <li> @shun |
| 440 | </ul></td></tr> |
| 441 | </table> |
| 442 | |
| 443 | <p>New configuration-names are likely to be added in future releases of |
| 444 | Fossil. If the server receives a configuration-name that it does not |
| 445 | understand, the entire reqconfig card is silently ignored. The reqconfig |
| 446 | card might also be ignored if the user lacks sufficient privilege to |
| 447 |
+1
-2
| --- www/tech_overview.wiki | ||
| +++ www/tech_overview.wiki | ||
| @@ -65,11 +65,11 @@ | ||
| 65 | 65 | SQLite's [http://www.sqlite.org/lang_attach.html | ATTACH] command. |
| 66 | 66 | |
| 67 | 67 | The chart below provides a quick summary of how each of these |
| 68 | 68 | database files are used by Fossil, with detailed discussion following. |
| 69 | 69 | |
| 70 | -<center><table border="1" width="80%" cellpadding="0"> | |
| 70 | +<table border="1" width="80%" cellpadding="0" align="center"> | |
| 71 | 71 | <tr> |
| 72 | 72 | <td width="33%" valign="top"> |
| 73 | 73 | <h3 align="center">Configuration Database<br>"~/.fossil"</h3> |
| 74 | 74 | <ul> |
| 75 | 75 | <li>Global [/help/setting |settings] |
| @@ -103,11 +103,10 @@ | ||
| 103 | 103 | <li>Information needed to "[/help/undo|undo]" or "[/help/redo|redo]" |
| 104 | 104 | </ul> |
| 105 | 105 | </td> |
| 106 | 106 | </tr> |
| 107 | 107 | </table> |
| 108 | -</center> | |
| 109 | 108 | |
| 110 | 109 | <h3>2.1 The Configuration Database</h3> |
| 111 | 110 | |
| 112 | 111 | The configuration database holds cross-repository preferences and a list of all |
| 113 | 112 | repositories for a single user. |
| 114 | 113 |
| --- www/tech_overview.wiki | |
| +++ www/tech_overview.wiki | |
| @@ -65,11 +65,11 @@ | |
| 65 | SQLite's [http://www.sqlite.org/lang_attach.html | ATTACH] command. |
| 66 | |
| 67 | The chart below provides a quick summary of how each of these |
| 68 | database files are used by Fossil, with detailed discussion following. |
| 69 | |
| 70 | <center><table border="1" width="80%" cellpadding="0"> |
| 71 | <tr> |
| 72 | <td width="33%" valign="top"> |
| 73 | <h3 align="center">Configuration Database<br>"~/.fossil"</h3> |
| 74 | <ul> |
| 75 | <li>Global [/help/setting |settings] |
| @@ -103,11 +103,10 @@ | |
| 103 | <li>Information needed to "[/help/undo|undo]" or "[/help/redo|redo]" |
| 104 | </ul> |
| 105 | </td> |
| 106 | </tr> |
| 107 | </table> |
| 108 | </center> |
| 109 | |
| 110 | <h3>2.1 The Configuration Database</h3> |
| 111 | |
| 112 | The configuration database holds cross-repository preferences and a list of all |
| 113 | repositories for a single user. |
| 114 |
| --- www/tech_overview.wiki | |
| +++ www/tech_overview.wiki | |
| @@ -65,11 +65,11 @@ | |
| 65 | SQLite's [http://www.sqlite.org/lang_attach.html | ATTACH] command. |
| 66 | |
| 67 | The chart below provides a quick summary of how each of these |
| 68 | database files are used by Fossil, with detailed discussion following. |
| 69 | |
| 70 | <table border="1" width="80%" cellpadding="0" align="center"> |
| 71 | <tr> |
| 72 | <td width="33%" valign="top"> |
| 73 | <h3 align="center">Configuration Database<br>"~/.fossil"</h3> |
| 74 | <ul> |
| 75 | <li>Global [/help/setting |settings] |
| @@ -103,11 +103,10 @@ | |
| 103 | <li>Information needed to "[/help/undo|undo]" or "[/help/redo|redo]" |
| 104 | </ul> |
| 105 | </td> |
| 106 | </tr> |
| 107 | </table> |
| 108 | |
| 109 | <h3>2.1 The Configuration Database</h3> |
| 110 | |
| 111 | The configuration database holds cross-repository preferences and a list of all |
| 112 | repositories for a single user. |
| 113 |