Re: [fossil-users] Set theme from command line
On Wed, 14 Mar 2012 21:10:21 +0100 Stephan Beal sgb...@googlemail.com wrote: On Wed, Mar 14, 2012 at 9:08 PM, Stephan Beal sgb...@googlemail.com wrote: specifically, you want to export a config from one e.g. fossil config export skin my.skin fossil config import my.skin should do the trick. Thanks. ___ 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] Compiling with digital Mars compiler
On 2012-03-14 19:36, Rene wrote:
I am checking if I could get polarssl compiled with dmc.
And to see if it would work with fossil compiled with dmc (and if
that still worked!).
The polarssl library compiling wasn't much of a problem. Mainly
creating a makefile for gnu make and
in 2 places I had to change
#ifdef _WIN32
in
#if defined(_WIN32) || defined(__DMC__)
in order to get vsnprintf and family recognized.
Compiling fossil
I ran into problems with winhttp.c because it uses
SERVICE_DESCRIPTION and dmc uses an old win32/winsvc.h
I copied winsvc.h from mingw and that worked.
Now I'm trying to compile sqlite3.c and ran into
{ AreFileApisANSI, (SYSCALL)AreFileApisANSI,
0 },
^
..\src\sqlite3.c(32280) : Error: constant initializer
expected
pMap = osMapViewOfFile(hMap, FILE_MAP_WRITE | FILE_MAP_READ,
^
..\src\sqlite3.c(34886) : Error: ')' expected
And I'm totally lost. Anyone a clue?
Thanks
if I change the 2 offending lines like so:
#define osAreFileApisANSI ((BOOL(WINAPI*)(VOID))aSyscall[0].pCurrent)
#define osAreFileApisANSI ((BOOL(WINAPI*)(void))aSyscall[0].pCurrent)
#define osMapViewOfFile
((LPVOID(WINAPI*)(HANDLE,DWORD,DWORD,DWORD,SIZE_T))aSyscall[47].pCurrent)
#define osMapViewOfFile
((LPVOID(WINAPI*)(HANDLE,DWORD,DWORD,DWORD,DWORD))aSyscall[47].pCurrent)
then sqlite3.c compiles.
I'm do not understand why that works!
--
Rene
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Pulling and pushing branches based on tags?
A thought that occurred to me that would be a nice feature to compliment our hopefully forthcoming per-branch push/pull implementation is the ability to do the same, but using a branch tag as the key. Take the following scenario as an example. A company has a product that is being worked on by a team of x developers. Each of the developers has a number of private branches where they do experimentation. The team shares a number of branches that are just for them (semi-public). And the company has set up a public facing (i.e., cgi website) branch for each of their clients for issue tracking and support (maybe 2 branches, one for issue tracking and another common one for documentation). It would be real nice to be able to assign a tag to each branch and then push/pull based off of that. So a developer can push/pull on tag = 'team' to work with the team's common branches, or pull tag = 'clients' to get an update on all the latest bug reports, or after having fixed a number of bugs for different clients, push tag = 'clients' to update the public side of things. I guess you could view this as just a grouping/convenience mechanism for the explicit branch push/pull, which hasn't even been implemented yet (but, that many of us hope will be soon). -- Christopher Berardi http://www.natoufa.com/ May grace and peace by yours in abundance. ___ 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] Pulling and pushing branches based on tags?
On Wed, Mar 14, 2012 at 3:13 PM, Christopher Berardi cbera...@natoufa.comwrote: A thought that occurred to me that would be a nice feature to compliment our hopefully forthcoming per-branch push/pull implementation is the ability to do the same, but using a branch tag as the key. Take the following scenario as an example. A company has a product that is being worked on by a team of x developers. Each of the developers has a number of private branches where they do experimentation. The team shares a number of branches that are just for them (semi-public). And the company has set up a public facing (i.e., cgi website) branch for each of their clients for issue tracking and support (maybe 2 branches, one for issue tracking and another common one for documentation). It would be real nice to be able to assign a tag to each branch and then push/pull based off of that. So a developer can push/pull on tag = 'team' to work with the team's common branches, or pull tag = 'clients' to get an update on all the latest bug reports, or after having fixed a number of bugs for different clients, push tag = 'clients' to update the public side of things. I guess you could view this as just a grouping/convenience mechanism for the explicit branch push/pull, which hasn't even been implemented yet (but, that many of us hope will be soon). Hi, I'm the slowpoke working on this feature. Fortunately for you, I considered exactly such a situation. Since a branch is essentially just a tag that propagates to descendants, any tag that has that property should work. You will have to create such tags via the commandline since the web interface doesn't appear to have a way to create propagating tags. -B ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
