[fossil-users] wiki link to tip zip archive
Is there a way to create a link to the zip archive on the tip of the trunk? I want the home page for my fossil archive to have a download link, but I have to update the link after every checkin, e.g. [b31d74a27c], and then tell people to click the zip archive link. Might there at least be a way for me to have a link to the tip checkin that I don't have to manually update? RW Ron Wilson, Engineering Project Lead (o) 434.455.6453, (m) 434.851.1612, www.harris.com HARRIS CORPORATION | RF Communications Division assuredcommunications(tm) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] wiki link to tip zip archive
On Sat, Dec 19, 2009 at 3:42 PM, D. Richard Hipp d...@hwaci.com wrote: http://www.projectname.org/fossil/zip/name-of-download.zip?uuid=trunk The trick is that the uuid= query parameter can specify a branch or a tag in addition to a specific check-in. Just out of curiosity: if a tag/branch name containing only hex (e.g. deadbeef) somehow collides with a version number, which takes preference? -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] wiki link to tip zip archive
D. Richard Hipp d...@hwaci.com wrote: http://www.projectname.org/fossil/zip/name-of-download.zip?uuid=trunk The trick is that the uuid= query parameter can specify a branch or a tag in addition to a specific check-in. Is there a way to make the name-of-download.zip dynamic? For instance, I can make it mailroom-trunk.zip, but which trunk? It would be nice to have a link such as /fossil/zip?uuid=trunk that would download and give the client the name such as mailroom-0bca30de.zip by itself so that the user would be able to identify the .zip file. Possibly something like /fossil/zip?uuid=trunkbasename=mailroom-snapshot- even would be nice. Jeremy ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Path Separators
-- Forwarded message -- From: Clark Christensen cdcmi...@yahoo.com To: fossil-us...@lists.fossil-scm.org Date: Fri, 18 Dec 2009 09:36:43 -0800 (PST) Subject: [fossil-users] Path Separators I'm using Fossil on MS Windows under the TCC/4NT shell, and am mostly really happy with it. But the one thing that causes me the most problems is the forward slash path separator in the output from many fossil commands. I often find myself using fossil status, then wanting to copy/paste a path/to/file from the output into the next command, perhaps fossil gdiff. Obviously, on Windows, this fails. And it's a hassle to have to edit the path separators every time. How do other Win/Fossil users handle this? Would it make sense to change Fossil to output backslashes as the path separator on Windows platforms (path\to\file)? Has this already been discussed? Thanks! -Clark I was also trying to use fossil under TCC, but I had problems with the space in the default COMSPEC location (c:\Programs Files... etc). Finally I gave up and now I have an alias FOSS=CMD /C D:\PROGRAMS\UTILS\FOSSIL.EXE This seems to work OK (I'm a quite basic fossil user yet though). I would be happy if fossil were made to work better under TCC and am willing to help with testing and suggestions (no coding in C). Emil ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Please contribute Fossil skins or themes
Earlier today, I checked in a version of Fossil that has the ability to host multiple themes or skins for the web interface and that allows users (with Admin privilege) to switch between skins with a simple mouse click. However, the current implementation contains only two built-in skins: The old default and a new black theme which is very similar to the default. It would be good, I think to have 6 to 10 different themes that show a wide variety of possible looks. Therefore, I am calling on the user community to submit themes for consideration. To create a new theme or skin, edit the CSS, header, and footer to obtain the look you want. Then run the following command: fossil configuration export skin outputfile.txt And post the outputfile.txt here. Thanks for contributing. D. Richard Hipp d...@hwaci.com ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Please contribute Fossil skins or themes
On Sat, Dec 19, 2009 at 10:28 PM, D. Richard Hipp d...@hwaci.com wrote: Earlier today, I checked in a version of Fossil that has the ability to host multiple themes or skins for the web interface and that allows users (with Admin privilege) to switch between skins with a simple mouse click. With version: step...@jareth:~/cvs/fossil/whalloc$ f ver This is fossil version [007d0a9b3f] 2009-12-19 21:04:29 UTC i'm getting Error 101 (net::ERR_CONNECTION_RESET): Unknown error from Google Chrome, 'reset by peer' from the links browser, and a timeout from wget when trying to connect to the local server. i've tried different ports, as well as localhost and over my dhcp address, but the same results. Platform=Linux x86/32, gcc 4.4.1 :-? Doesn't server mode have some sort of trace/debug option? -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Please contribute Fossil skins or themes
Op Za, 19 december, 2009 22:28, schreef D. Richard Hipp:
Earlier today, I checked in a version of Fossil that has the ability
to host multiple themes or skins for the web interface and that
allows users (with Admin privilege) to switch between skins with a
simple mouse click.
However, the current implementation contains only two built-in skins:
The old default and a new black theme which is very similar to the
default. It would be good, I think to have 6 to 10 different themes
that show a wide variety of possible looks. Therefore, I am calling
on the user community to submit themes for consideration.
To create a new theme or skin, edit the CSS, header, and footer to
obtain the look you want. Then run the following command:
fossil configuration export skin outputfile.txt
And post the outputfile.txt here. Thanks for contributing.
D. Richard Hipp
d...@hwaci.com
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
Rene de Zwart-- The skin configuration exported from
-- repository /home/renez/src/myclone.fossil
-- on 2009-12-20 03:54:14
REPLACE INTO config VALUES('css','/* General settings for the entire page */
body {
margin: 0ex 1ex;
padding: 0px;
background-color: white;
font-family: sans-serif;
}
/* The project logo in the upper left-hand corner of each page */
div.logo {
display: table-cell;
text-align: center;
vertical-align: bottom;
font-weight: bold;
color: #558195;
}
/* The page title centered at the top of each page */
div.title {
display: table-cell;
font-size: 2em;
font-weight: bold;
text-align: left;
padding: 0 0 0 1em;
color: #558195;
vertical-align: bottom;
width: 100%;
}
/* The login status message in the top right-hand corner */
div.status {
display: table-cell;
text-align: right;
vertical-align: bottom;
color: #558195;
font-size: 0.8em;
font-weight: bold;
}
/* The header across the top of the page */
div.header {
display: table;
width: 100%;
}
/* The main menu bar that appears at the top of the page beneath
** the header */
div.mainmenu {
padding: 5px 10px 5px 10px;
font-size: 0.9em;
font-weight: bold;
text-align: center;
letter-spacing: 1px;
background-color: #558195;
color: white;
}
/* The submenu bar that *sometimes* appears below the main menu */
div.submenu {
padding: 3px 10px 3px 0px;
font-size: 0.9em;
text-align: center;
background-color: #456878;
color: white;
}
div.mainmenu a, div.mainmenu a:visited, div.submenu a, div.submenu a:visited {
padding: 3px 10px 3px 10px;
color: white;
text-decoration: none;
}
div.mainmenu a:hover, div.submenu a:hover {
color: #558195;
background-color: white;
}
/* All page content from the bottom of the menu or submenu down to
** the footer */
div.content {
padding: 0ex 1ex 0ex 2ex;
}
/* Some pages have section dividers */
div.section {
margin-bottom: 0px;
margin-top: 1em;
padding: 1px 1px 1px 1px;
font-size: 1.2em;
font-weight: bold;
background-color: #558195;
color: white;
}
/* The Date that occurs on the left hand side of timelines */
div.divider {
background: #a1c4d4;
border: 2px #558195 solid;
font-size: 1em; font-weight: normal;
padding: .25em;
margin: .2em 0 .2em 0;
float: left;
clear: left;
}
/* The footer at the very bottom of the page */
div.footer {
font-size: 0.8em;
margin-top: 12px;
padding: 5px 10px 5px 10px;
text-align: right;
background-color: #558195;
color: white;
}
/* Make the links in the footer less ugly... */
div.footer a { color: white; }
div.footer a:link { color: white; }
div.footer a:visited { color: white; }
div.footer a:hover { background-color: white; color: #558195; }
/* verbatim blocks */
pre.verbatim {
background-color: #f5f5f5;
padding: 0.5em;
}
/* The label/value pairs on (for example) the ci page */
table.label-value th {
vertical-align: top;
text-align: right;
padding: 0.2ex 2ex;
}
/* For marking important UI elements which shouldn''t be
lightly dismissed. I mainly use it to mark not yet
implemented parts of a page. Whether or not to have
a ''border'' attribute set is arguable. */
.achtung {
color: #ff;
background: #00;
border: 1px solid #ff;
}
div.miniform {
font-size: smaller;
margin: 8px;
}
#nav, #nav ul {
float: left;
width: 100%;
list-style: none;
line-height: 1;
background: white;
font-family: sans-serif;
font-weight: bold;
padding: 0;
border: solid #558195;
border-width: 1px 0;
margin: 0 0 1em 0;
}
#nav a {
display: block;
width: 10em;
w\idth: 6em;
color: #558195;
text-decoration: none;
padding: 0.25em 2em;
}
#nav a.daddy {
background: url(/ckout/arrow_right.png) center right no-repeat;
}
#nav li {
float:
Re: [fossil-users] file artifact links not working
actually what is happening is that fossil.exe launches another fossil process to serve the artifact and that process crashes. the _in txt file has GET /artifact info but the _out txt file is null. from my mobile 434.851.1612 On Dec 19, 2009, at 7:06 PM, Wilson, Ronald rwils...@harris.com wrote: on one of my new repositories the file artifact links don't work for files with extension .zrx. these are simple windows text files. other file artifacts work fine. try it yourself here http://svn.thereverend.org:8080/ check the history of any zrx file then click the link for it's artifact and the server will return error 324. any help would be appreciated. from my mobile 434.851.1612 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
