Re: [fossil-users] How to avoid 'touching' the fossil repo for read-only operation?
Hmm, I may not know the internals of how fossil works, but I have these observations: * this seems kind of pointless, given I can open the same repo in multiple locations at the same time. Are you sure you're not referring to the separate _FOSSIL_ database, instead, or some special operation that changes that table? * it doesn't seem to be the actual reason as I ran your query on my various fossils, and many of them return zero rows or very few rows compared to the number of opens it went through so far. * please note that opening the repo using the UI interface, looking around, and even downloading single files, does not change the database at all. How can this interface manage to do all this work without a single write to the database? -Original Message- From: Andy Bradford Sent: Saturday, August 09, 2014 8:24 PM To: Tony Papadimitriou Cc: Fossil SCM user's discussion Subject: Re: [fossil-users] How to avoid 'touching' the fossil repo for read-only operation? Thus said Tony Papadimitriou on Sat, 09 Aug 2014 20:01:30 +0300: Every time I open a fossil repo, even if I simply open it to just get a copy of the files in some directory, I end up with a 'touched' repo file, as if some 'write' operation has occurred in the database. Every time fossil opens a repository it records the path in the repository: $ pwd /tmp/new $ echo SELECT * FROM config WHERE name LIKE 'ckout:%'; | fossil sql ckout:/tmp/new/|1|1407604257 ckout:/tmp/another/|1|1407604319 Andy -- TAI64 timestamp: 400053e65971 ___ 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] How to export ala CVS?
Thanks to both you and Andy for your explanations. fossil zip seems like a great solution for what I need. Now, if there was a matching ‘unzip’ to do the hypothetical unzipping and serve the files as is, it would be even greater! (The name ‘unzip’ only as a mental opposite to ‘zip’, not to suggest than an unzipping operation should follow the zipping but to skip simply over the zipping part.) Thanks. From: Stephan Beal Sent: Saturday, August 09, 2014 9:31 PM To: Fossil SCM user's discussion Subject: Re: [fossil-users] How to export ala CVS? On Sat, Aug 9, 2014 at 8:30 PM, Andy Bradford amb-fos...@bradfords.org wrote: Does Fossil have an option that exports a particular revision of the repository similar to how CVS export works? CVS export will export either HEAD or an explicit revision to a named directory without all the CVS control directories/files in the export. As far as I can tell, the only way to get it is: fossil open REPO VERSION fossil close Or: fossil zip trunk my.zip resp. tar. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ 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] Problem with using branch names
Figured it out. It is case sensitive, I branched as WIP and tried with “wip”. Sorry for the noise. From: Tony Papadimitriou Sent: Friday, August 08, 2014 9:01 PM To: Fossil SCM user's discussion Subject: [fossil-users] Problem with using branch names This is fossil version 1.29 [3e5ebe2b90] 2014-06-12 17:25:56 UTC (f = fossil) I created a branch with the F COMMIT --BRANCH WIP command (WIP is the name of the branch I created) . Then if I do F UP TRUNK it switches to trunk, no problem. Then I try F UP WIP and it gives this error: “no such version: wip” But in the timeline, I can see this version with “tags: WIP”, and if I use F UP with the hash value instead it loads it. So, it simply does not accept the branch name as a version. Isn’t the use of a branch or tag name a shortcut for the latest version carrying that tag? Why doesn’t it work? (I have a feeling it used to work, but now I must be doing something differently, and I can’t figure out what.) Thanks. ___ 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
[fossil-users] Error compiling current trunk with VC
I get this with trying to compile [78fdf9f5b2] with MSVC. Any ideas? ... zlib.lib ws2_32.lib advapi32.lib zlib.lib(zutil.obj) : warning LNK4217: locally defined symbol _free imported in function _zcfree zlib.lib(zutil.obj) : warning LNK4217: locally defined symbol _malloc imported in function _zcalloc sqlite3.obj : error LNK2001: unresolved external symbol __InterlockedCompareExchange .\fossil.exe : fatal error LNK1120: 1 unresolved externals NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 12.0\VC\BIN\link.EXE' : return code '0x460' Stop. ___ 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] Error compiling current trunk with VC
The problem appeared in [5ce85eb6f8] Upgrade the built-in SQLite to the latest 3.8.6 alpha from upstream. (user: mistachkin tags: trunk) -Original Message- From: Tony Papadimitriou Sent: Wednesday, August 06, 2014 12:15 PM To: Fossil SCM user's discussion Subject: [fossil-users] Error compiling current trunk with VC I get this with trying to compile [78fdf9f5b2] with MSVC. Any ideas? ... zlib.lib ws2_32.lib advapi32.lib zlib.lib(zutil.obj) : warning LNK4217: locally defined symbol _free imported in function _zcfree zlib.lib(zutil.obj) : warning LNK4217: locally defined symbol _malloc imported in function _zcalloc sqlite3.obj : error LNK2001: unresolved external symbol __InterlockedCompareExchange .\fossil.exe : fatal error LNK1120: 1 unresolved externals NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 12.0\VC\BIN\link.EXE' : return code '0x460' Stop. ___ 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
[fossil-users] Unexpected SQLITE_IOERR
This is fossil version 1.29 [09f2386328] 2014-04-28 12:24:17 UTC On a Win7 machine, during FOSSIL CHANGES command, I got this error “SQLITE_IOERR: delayed 25ms for lock/sharing conflict” I’m neither running concurrent FOSSIL sessions, nor do I have the fossil file open with SQLite3, so this is simply an unexpected lock or delay timeout (perhaps due to the Win OS being late to report something back to the app – I don’t know). So I guess either the delay is too small, and it should be made a little longer, or there is something else wrong with the code. This is the kind of error you can’t reproduce on demand, so I’m just reporting it happened. Thanks.___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Problem: Can't get diff against renamed file
If I rename a file (both on disk and with FOSSIL REN command), and then try to do a [G]DIFF command –FROM a date where the file had the old name, I get the message that the file does not exist in that checkin. So, once I rename a file I lose the connection to all its history and the changes made to it? I understand it now has a different name, but it seems to me that part of keeping history of changes is to also know that the name changed, so if I want to get the diff from version A to version B it should do so even if the file has changed names between the two versions (because FOSSIL knows – or should know -- about this change of name). I also suspect (but haven’t tested to see if it is so) that if the old checkin happened to have a file with the same name as the current version’s renamed one (but the old version’s was at some point either renamed or deleted), FOSSIL would try to give me the DIFF between two completely unrelated files. That just doesn’t seem correct behavior. Comments? ___ 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] Problem: Can't get diff against renamed file
Stephan Beal wrote: Correct, because fossil's only way of knowing the identity of a file is its name. If you take my name, everyone will think you're me. Nothing i can do about that. The SHA1 unique identifies the version of the content, but the name gives us a place under which to organize that. I see the simplistic approach. On the other hand, if I decided to change my name at some point, the authorities should be able to trace my current name to my birth name, to figure out who I am, and my ‘criminal’ record should not disappear!!! Anyway, (as a future enhancement, perhaps) if FOSSIL knows in its trail of changes from version A to version B that a file was renamed it should be able to figure out and locate the correct file (by name) in the old version and do a correct DIFF, while giving the “doesn’t exist” error if the file was not yet introduced (by ADD or ADDR). And, obviously, FOSSIL does know, as it can be seen from the UI (“Name change from ... to ...”). Of course that would mean that to find what filename to compare it with, it should do a walk-thru of all intermediate checkins from A to B, and not just look at the two versions as two independent checkins (which I suspect is what happens now) without regard to what happened in between (and I mean only in relation to name changes, of course, not their contents). 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] Suggestion about fossil commit
I often have the same problem for a different reason. I type “f cha” and “f com” so often that sometime instead of “f cha” I accidentally type “f com”. What I would like to have is an extra prompt, “Are you sure (y/N)?” with No default for commits. Since commits are irreversible, I think the extra prompt to safeguard against typing accidents will be welcome by most users without adding too much burden to each commit. Then again, it could also be activated via some setting so those who don’t want it can do without it. Tony P. From: Stanislav Paskalev Sent: Monday, April 14, 2014 2:41 AM To: Fossil SCM user's discussion Subject: [fossil-users] Suggestion about fossil commit Hi fossil-devs, I often reuse a console to work with fossil as well as something else (e.g. compile, run tests, etc) Due to my trigger-happy fingers I've had quite a few cases where I inadvertently ran fossil commit -m .. from history when in reality I wanted to run my tests for example. Fossil could compare the current message against the latest checkin in the active branch and warn if they match. If this sounds fine - I can make and send a patch :) Regards, Stanislav Paskalev ___ 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] Suggestion about fossil commit
WHAT? Oh, this is embarrassing... All this time I've been typing something (like the word 'ACCIDENT') in the editor thinking I have already started the commit process and I would complete the commit when I exit the editor, so I always typed something to know that this commit was a mistake. I didn't know that typing nothing would cancel the operation. But, in my defense, (and I just re-read it to be sure I didn't miss it) nowhere in the help documentation (FOSSIL HELP COMMIT) or the comment in the editor (# Enter commit message for this check-in. Lines beginning with # are ignored.) does it say, or even imply, that an empty comment is one of the reasons that will 'abort' the commit. LOL!!! Thanks. -Original Message- From: Martin Gagnon Sent: Monday, April 14, 2014 3:24 PM To: Fossil SCM user's discussion Subject: Re: [fossil-users] Suggestion about fossil commit On Mon, Apr 14, 2014 at 02:55:51PM +0300, Tony Papadimitriou wrote: I often have the same problem for a different reason. I type “f cha” and “f com” so often that sometime instead of “f cha” I accidentally type “f com”. What I would like to have is an extra prompt, “Are you sure (y/N)?” with No default for commits. Since commits are irreversible, I think the extra prompt to safeguard against typing accidents will be welcome by most users without adding too much burden to each commit. Then again, it could also be activated via some setting so those who don’t want it can do without it. Since fossil commit start an editor and having empty commit message give you a kind of Are you sure prompt already, how can you commit by mistake when typing f com instead of f cha ? It's not like you will type: f com -m some text when you were about to type f cha ... Regards. -- Martin G. ___ 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
[fossil-users] FIND command inconsistency [69974aaa19]
Hi all, Before I get to the problem I noticed, a little ‘complaint’: I find the fact that many commands work on all branches by default (and without possibility of overriding that default) problematic. If I’m inside a certain branch then I logically (most of the time, at least) only care to see things related to that branch because at that moment I don’t care what’s going on any other branches. Although an option (for all commands) to allow me to run it against the whole tree would be great when I need a fuller picture. But, looking at the whole tree at all time is counter productive (and sometimes even confusing/misleading if you’re not careful enough to notice the branch tag, for example with FOSSIL TIMELINE command), in my opinion. Anyway, now to the specific problem with FIND: I have a file xxx that appears in several branches. If I’m on the ‘trunk’ branch for example, and type FOSSIL FIND xxx I will get a list of all changes for xxx in all branches (not just trunk). Now, I have another branch where the file xxx is deleted. From that branch, FOSSIL FIND xxx no longer shows any history from the xxx file. Why is it that from a branch that xxx exists I can see xxx in any other branch but from a branch where xxx is missing I cannot see the xxx’s in the other branches? It should be either I can see it in all branches at all times, or on my current branch at all times. Is this a bug, or am I not using the system correctly? 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] FINFO command inconsistency [69974aaa19]
And of course I mean FINFO (not FIND), but I always type it as F and in my mind it got memorized as FIND. From: Tony Papadimitriou Sent: Tuesday, April 08, 2014 6:43 PM To: Fossil SCM user's discussion Subject: [fossil-users] FIND command inconsistency [69974aaa19] Hi all, Before I get to the problem I noticed, a little ‘complaint’: I find the fact that many commands work on all branches by default (and without possibility of overriding that default) problematic. If I’m inside a certain branch then I logically (most of the time, at least) only care to see things related to that branch because at that moment I don’t care what’s going on any other branches. Although an option (for all commands) to allow me to run it against the whole tree would be great when I need a fuller picture. But, looking at the whole tree at all time is counter productive (and sometimes even confusing/misleading if you’re not careful enough to notice the branch tag, for example with FOSSIL TIMELINE command), in my opinion. Anyway, now to the specific problem with FIND: I have a file xxx that appears in several branches. If I’m on the ‘trunk’ branch for example, and type FOSSIL FIND xxx I will get a list of all changes for xxx in all branches (not just trunk). Now, I have another branch where the file xxx is deleted. From that branch, FOSSIL FIND xxx no longer shows any history from the xxx file. Why is it that from a branch that xxx exists I can see xxx in any other branch but from a branch where xxx is missing I cannot see the xxx’s in the other branches? It should be either I can see it in all branches at all times, or on my current branch at all times. Is this a bug, or am I not using the system correctly? Thanks. ___ 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] Is it possible to see timeline for given branch (or eventag)?
I tried it. r still finds “related” items in any branch. So, if you happen to use the name of a branch anywhere inside the description it will pick it up, too even in a different branch. t= for tags seems to work fine. Maybe add b= for branch? But, also it would be nice to do this from the CLI. Thanks. From: Stephan Beal Sent: Thursday, March 27, 2014 7:43 PM To: Fossil SCM user's discussion Subject: Re: [fossil-users] Is it possible to see timeline for given branch (or eventag)? On Thu, Mar 27, 2014 at 6:31 PM, Tony Papadimitriou to...@acm.org wrote: When I give the command FOSSIL TIM it lists all changes in all branches (and tags). But what if I want to see changes in only, say, the TRUNK branch? Is there a way? Or maybe items having a given tag? i've just been experimenting, and while i thought one could filter exclusively on a specific branch, i don't see a way to do it via the CLI. In the www interface, adding r=BRANCHNAME will do the trick: http://www.fossil-scm.org/index.html/timeline?r=branch-1.28 -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ 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
[fossil-users] Different line endings do not mean different text!!!
Hi all, While converting some text files from CRLF (Windows) to LF (Linux) endings, and committing the changes, I noticed this very annoying issue during DIFF: Every single line (the whole line) of the current and previous version (which only differ by the line ending) appears to have changed. Although technically the line ending itself has changed (and not the whole line text), and I could understand some color appearing at the end of each line indicating this difference, 1. I don't think it should highlight the whole line as different. 2. I still think the correct display would be to show no changes at all (all text should be white) because for text files, what makes a file really different is the text itself, not the line endings which can be altered when moving files back and forth between Windows/Linux/Mac. At any rate, maybe there is an option to not show line ending differences are being different, and avoid this confusing display of colors for same text? TIA ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
