Re: [fossil-users] Commit failing... retyping commit message
i completely agree with "lets keep options to a minimum" and i appreciate the comment "we shouldn't mind code complexity" so .. might i suggest that -m be overloaded?? so both of these would work.. fossil commit -m ./file.txt would fossil commit -m "commit message" essentially -m would first check to see if resolves to a valid file, otherwise take to be the comment text.. Daniel On 10/12/2009 1:58 PM, Jeremy Cowgar wrote: > Stephan Beal wrote: > >> On Thu, Dec 10, 2009 at 12:48 AM, Wilson, Ronaldwrote: >> >> >>> I like DRH's idea but I agree with others that a --comment-file|-M >>> feature is needed for integration applications. However, I think >>> --comment-file could be less verbose and -M is begging for caps-lock >>> confusion. I suggest --infile|-i COMMENT-FILE-NAME. >>> >>> >>> >> i apologize to all - i didn't mean to open up a can of worms. i'll wait on >> DRH's vote/veto, and commit (or not). If i do, i'll change it to --infile/-i >> unless there are strong objections. For those of you who want it now, the >> diff is in one of the previous posts. >> >> > I personally would be confused looking at just an option list: > > fossil commit [-m|--message commit-message] [-i|--infile filename] [...] > [file] > > Infile what? I wouldn't worry about --comment-file, it may seem a bit verbose > but who's going to use that directly? tools for clarity, but for users, they > would use -M (or whatever it winds up being). Actually, thinking about it, > I'd keep both -M and --commit-file. If they mess up and type fossil commit -M > "Commit Message" they will get an error: > > File 'Commit Message' could not be opened. > > Now, look at: > > fossil commit -m|--message commit-message] [-M|--message-file filename] [...] > [file] > > It makes sense with no further help information. > > Jeremy > > ___ > 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
Re: [fossil-users] cross compilling fossil
no, but that is mostly due to a lack of time to play recently :) its not causing me enough pain for me to really need to fix it.. so for now it remains a 'gee that would be nice' type thing.. cheers Daniel On 2/12/2009 5:29 AM, Rene de Zwart wrote: > daniel, > > I'm just being curious :-) Did you succeed in cross-compiling linux on > windows? > > ___ 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] cross compilling fossil
I'm still chasing some details on whether its possible to cross compile a 64bit linux version of fossil from within mingw on win32.. I do realise that request sounds a bit odd, but I actually *enjoy* developing on windows, and have solved almost all the dependency challenges that have been thrown at me, but my knowledge of all the command line options to gcc is nowhere near good enough to solve this one.. Anybody?? On 23/11/2009 5:07 AM, Rene de Zwart wrote: > I have been looking at cross compiling fossil and have a bit less > intrusive instructions because the Makefile already have a provision for > cross-compiling. > > 1) Install mingw32-gcc on arch you type Pacman -S mingw32-gcc > 2) download zlib unpack and > CC=i486-mingw32-gcc ./configure > i486-mingw32-ranlib libz.a > 3) Become root and cp libz.a, zconf.h and zlib.h to the mingw dirs mine > cp libz.a /usr/i486-ming32/lib > cp zconf.h zlib.h /usr/486-mingw32/include > exit from root > You kan remove the zlib source it is not needed anymore. > 4) edit Makefile and Makefile.w32 > a) add a line "TARGETCC=gcc" > b) Change gcc in every TCC= line to $(TARGETCC) > > 5) if you want to create windows binary do > make -f Makefile.w32 TARGETCC=i486-mingw32-gcc > > 6) if you have installed wine and want to a have wine binary > make TARGETCC=winegcc > > Perhaps the under 4 mentioned changes can be added to the Makefiles by > someone with checkin capabilities? > > ___ 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] Zip files won't unzip on OS X
i know what that paragraph is saying, but read it again with newbie to fossil eyes and there is a very real chance that confusion will set in.. shouldn't the permissions system be setup so it would read.. "I've set it up so that _anybody_ can clone" *** markdown included intentionally - i couldn't help myself :) On 30/11/2009 12:57 PM, Will Duquette wrote: > I thought that might be the case, but I wasn't sure. I've set > it up so that nobody can clone. Alternatively, you can log in > as anonymous and use the Zip Archive link on the Leaf page. > Or you can download glue.kit. > > Will > > On Nov 29, 2009, at 6:32 PM, chi wrote: > > >> >> Will Duquette wrote: >> >>> Anonymous can clone it, according to the Users page. I've not tried >>> that myself. >>> >>> >> Hmmm ... if I try, fossil means, that anonymous have no rights to >> clone >> the repository. If you look onto the User page, what password user >> anonymous posses? Perhaps it is some hex value, then cloning is not >> very >> easy ;-) >> >> In the past, if a repository was new created, every anonymous got the >> password 'anonymous'. But since some time, every new created >> repository >> get a random password for anonymous. If I do not know this, I cannot >> clone the repos despite the permission. >> >> If this is the case, you would have either to change and publish the >> anonymous password for users that would like to clone (the login >> password for anonymous will still be generated automatically to be >> different for every login), or you would have to allow user nobody to >> clone ... >> >> Ciao, >> chi. >> >> (...) >> >> ___ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> > -- > will -at- wjduquette.com | Catch our weblog, > http://foothills.wjduquette.com/blog | The View from the Foothills > > > ___ > 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
Re: [fossil-users] makefile.w32
should be around line 20.. The suffix to add to executable files. ".exe" for windows. #Nothing for unix. # -E = +E = .exe the only other change i have made is to set the INSTALLDIR variable, but that is a bit too system specific to set in a shared makefile.. also, has anyone got any pointers as to how I would compile a linux 64bit executable with mingw on x86/win32? is it even possible i would like to keep my server version up to date with my local one and don't want to have to build an entire linux install just to build a single app.. cheers Daniel On 20/10/2009 10:45 AM, Wilson, Ronald wrote: >> Sounds fine to me, while you are there, can you also change add the >> E = .exe suffix? >> >> one less change i have to keep locally.. >> > I'm not familiar with that parameter. what line should change? spell > it out and I'll try it tomorrow. > > 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
Re: [fossil-users] makefile.w32
Sounds fine to me, while you are there, can you also change add the E = .exe suffix? one less change i have to keep locally.. On 20/10/2009 3:51 AM, Wilson, Ronald wrote: Does anyone object to the following makefile changes for win32? I can check them in if there are no objections. PS C:\fossil\fossil> fossil diff Makefile.w32 --- Makefile.w32 +++ Makefile.w32 @@ -25,24 +25,25 @@ # for building intermediate code-generator tools. # #TCC = gcc -O6 #TCC = gcc -g -O0 -Wall -fprofile-arcs -ftest-coverage #TCC = gcc -g -Os -Wall -TCC = gcc -g -Os -Wall -DFOSSIL_I18N=0 -L/usr/local/lib -I/usr/local/include +#TCC = gcc -g -Os -Wall -DFOSSIL_I18N=0 -L/usr/local/lib -I/usr/local/include +TCC = gcc -Os -Wall -DFOSSIL_I18N=0 -L/mingw/lib -I/mingw/include Extra arguments for linking the finished binary. Fossil needs # to link against the Z-Lib compression library. There are no # other dependencies. We sometimes add the -static option here # so that we can build a static executable that will run in a # chroot jail. # #LIB = -lz -LIB = -lz -lws2_32 - +#LIB = -lz -lws2_32 +LIB = -lmingwex -lz -lws2_32 Tcl shell for use in running the fossil testsuite. # TCLSH = tclsh # You should not need to change anything below this line ### include $(SRCDIR)/main.mk Ron Wilson, Engineering Project Lead (o) 434.455.6453, (m) 434.851.1612, www.harris.com HARRIS CORPORATION | RF Communications Division assuredcommunications™ NOTICE: This e-mail transmission (and any of its attachments) may contain confidential, proprietary and/or privileged information. The sender intends this transmission only for the designated recipient(s). If you are not a designated recipient (or authorized to receive for a designated recipient), you are hereby notified that the disclosure, copying, distribution or use of any of the information contained in this transmission is strictly prohibited. If you have received this transmission in error, please destroy this message, delete any copies which may exist on your system and notify the sender immediately. Thank you. ___ 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
