Re: [fossil-users] What is changes or status trying to tell me when it lists files as "MISSING"?

stephan, >> In this case what MISSING was really trying to tell me was that my >> sandbox wasn't at the revision I thought it was. > > That's not quite right - MISSING means that the checkout knows about the > files, but can't find them (because you rm'd them). In the literal sense, yes. But (i

Re: [fossil-users] What is changes or status trying to tell me when it lists files as "MISSING"?

On Sat, Jun 28, 2014 at 2:37 AM, Shal Farley wrote: > In this case what MISSING was really trying to tell me was that my sandbox > wasn't at the revision I thought it was > That's not quite right - MISSING means that the checkout knows about the files, but can't find them (because you rm'd them)

Re: [fossil-users] What is changes or status trying to tell me when it lists files as "MISSING"?

Richard, Ok, thanks. Rather than be too clever, revert followed by update cleared this up for me. Sort of the same answer, revert put the missing files back, update deleted them, and now my status has no complaints, as it should be. In this case what MISSING was really trying to tell me was

[fossil-users] Problem accessing shared folder in VirtualBox

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/27/2014 5:56 PM, Alexander Strobel wrote: > Problem: I am getting the following error message when I try to > open a repo wich lies in a shared folder of Oracles VirtualBox: > [somelocaldir]$ fossil open ../geelaunch.fossil SQLITE_IOERR: > os_uni

Re: [fossil-users] What is changes or status trying to tell me when it lists files as "MISSING"?

I think your next "commit" attempt will fail unless you either "fossil rm" the missing files, or create files with appropriate names so that they are no longer missing. On Fri, Jun 27, 2014 at 7:04 PM, Shal Farley wrote: > These are files which I had previously committed in this sandbox, checke

[fossil-users] What is changes or status trying to tell me when it lists files as "MISSING"?

These are files which I had previously committed in this sandbox, checked out in another sandbox, realized during some development in that sandbox that they shouldn't have been in the repository in the first place and rm'd them there. Now I'm back in the original sandbox and have updated, most

[fossil-users] Problem accessing shared folder in VirtualBox

Problem: I am getting the following error message when I try to open a repo wich lies in a shared folder of Oracles VirtualBox: [somelocaldir]$ fossil open ../geelaunch.fossil SQLITE_IOERR: os_unix.c:29821: (22) fsync(/media/sf_Projects/geelaunch_working/../geelaunch.fossil-mjC43B7293F) - Invalid

Re: [fossil-users] Sixteen-digit event IDs

Thus said Andy Goth on Fri, 27 Jun 2014 16:40:33 -0500: > How come events are always shown with (at least) sixteen digits on the > timeline whereas other artifacts are given ten digits? Perhaps because prior to [49467d2a494] short events that collided with other types of artifacts were silently

[fossil-users] Sixteen-digit event IDs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 How come events are always shown with (at least) sixteen digits on the timeline whereas other artifacts are given ten digits? http://www.fossil-scm.org/fossil/timeline?n=20&y=e - -- Andy Goth | -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (

Re: [fossil-users] Fuse SIGSEGV

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/27/2014 11:51 AM, Andy Goth wrote: > On 6/26/2014 7:11 PM, Andy Goth wrote: >> On 6/26/2014 3:39 PM, Richard Hipp wrote: >>> Since you are able to repro this, can you rebuild Fossil w/o >>> the -O2 option (so that variables are not optimized out)

Re: [fossil-users] Fuse SIGSEGV

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/26/2014 7:11 PM, Andy Goth wrote: > On 6/26/2014 3:39 PM, Richard Hipp wrote: >> Since you are able to repro this, can you rebuild Fossil w/o the >> -O2 option (so that variables are not optimized out) and rerun >> in the debugger yet again, then

Re: [fossil-users] switching between checkouts, best practices

On Fri, Jun 27, 2014 at 4:56 PM, Michai Ramakers wrote: > slight revisit of this post: > > http://lists.fossil-scm.org:8080/pipermail/fossil-users/2014-March/015613.html > > How do you normally switch between checkouts (assuming there are no > local changes)? I'd use either 'update' or 'checkout'

Re: [fossil-users] switching between checkouts, best practices

On 06/27/2014 05:56 PM, Michai Ramakers wrote: > I noticed 'checkout --force' is rather slow (didn't investigate > further or try on different machines), and thus I wonder how silly > this is compared to just opening the repo multiple times - once for > each desired checkout/tag. > > Any ideas? Y

[fossil-users] switching between checkouts, best practices

Hello, slight revisit of this post: http://lists.fossil-scm.org:8080/pipermail/fossil-users/2014-March/015613.html How do you normally switch between checkouts (assuming there are no local changes)? I'd use either 'update' or 'checkout', but both can leave files that were not originally in the ta

Re: [fossil-users] Generous time formats

On Fri, Jun 27, 2014 at 9:11 AM, Jan Nijtmans wrote: > Just my 2c. Since fossil depends on SQLite for its date > functions, I think this is intentional. See: > > As a side-note: the /reports pages use Week #0 in some cases... because sqlite3 does it

Re: [fossil-users] Do the default binaries use mingw files? [or what build method was used?]

2014-06-27 0:49 GMT+02:00 Kevin Ar18 : > Do these binaries (for Windows) use mingw files? or are they entirely MSVC? > (Or, in other words, which of the several build methods were used for the > binaries?) . > http://www.fossil-scm.org/fossil/doc/trunk/www/build.wiki > http://www.fossil-scm.or

Re: [fossil-users] Generous time formats

2014-06-27 2:07 GMT+02:00 Andy Goth : > Fossil accepts dates with days beyond the end of the month, so long as > the day is not 32 or greater. It also accepts times 24:00:00 through > 24:59:59. > > For example, 2014-02-31T24:59:59 is valid. I imagine it means 31 days > after the start of the day