[fossil-users] "Git horror story" post.

2014-05-31 Thread B Harder
http://mikegerwitz.com/papers/git-horror-story ___ 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] working checkout does not match what would have ended up in the repository

2014-05-31 Thread Stephan Beal
Also briefly from the tablet (in bed)... the current impl maintains the historical behaviour by default, while making the new behaviour available via a flag (-empty, though feel free to suggest a name). Will look through my chat logs tomorrow - our discussion was there, i think. (sent from a mobi

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-31 Thread B Harder
Stephan - i'm on mobile ATM so will be brief, but you and I did discussed this offline weeks ago whereby I thought we agreed that changing the text of the initial commit to something symbolic ("."?) or inoffensive Latin ("seed ", "origin") really would fit the bill without rejigging core fossil ope

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-31 Thread Stephan Beal
On Sat, May 31, 2014 at 9:40 PM, Stephan Beal wrote: > [stephan@host:~/tmp]$ f-timeline -R x3.fsl > checkin [e63f7616798d] @ 2010-01-01 02:02:03 by [stephan] branch [trunk] > > initial empty check-in > > Hmmm (unrelated)... timestamp doesn't take into account summer time diff. > CET is currently

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-31 Thread Stephan Beal
On Sat, May 31, 2014 at 4:33 PM, Stephan Beal wrote: > Once i'm back from shopping i'll work on a patch which reverts to the > previous default behaviour and adds a new flag for those who want to > create/play with an empty repo (which still likely has open corner cases > involving RID 0). > i'v

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-31 Thread Michai Ramakers
On 31 May 2014 18:49, Stephan Beal wrote: > > Am i wrong, or did Joel's patch just correct the problem: seems to work here too, with some simple examples. Michai ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.or

Re: [fossil-users] working with open source code

2014-05-31 Thread Andy Bradford
Thus said Abilio Marques on Sat, 31 May 2014 00:12:00 -0430: > Let's say I want to do this setup: > Clone sqlite repo on a local server > Then clone the server into several machines, with the users pushing > changes Are they committing changes to trunk? > Then, someday, I will want to update

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-31 Thread Andy Bradford
Thus said Stephan Beal on Sat, 31 May 2014 18:49:09 +0200: > Am i wrong, or did Joel's patch just correct the problem: Yes, it does appear to correct it: $ ../fossil ver This is fossil version 1.29 [1a0179abd7] 2014-05-31 16:37:06 UTC $ ../fossil info | grep checkins checkins: 0 $ jot -w 'fi

Re: [fossil-users] use of 'fossil close'

2014-05-31 Thread Stephan Beal
On Sat, May 31, 2014 at 6:58 PM, Michai Ramakers wrote: > My test was a bit silly - repo perms were set 444, but owned > michai.users, and executed as 'michai', sorry, let's do that again. > r/o should work, in the sense of it "shouldn't fail, but won't do much." (For those who don't know 0444 =

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-31 Thread Joel Bruick
Stephan Beal wrote: Am i wrong, or did Joel's patch just correct the problem: I hope so. The commit I backed out seems to serve no purpose besides messing up vfile_aggregate_checksum_disk(). Specifically, this part from the function's documentation: ** Newly added files that are not contain

Re: [fossil-users] use of 'fossil close'

2014-05-31 Thread Michai Ramakers
On 31 May 2014 18:21, Stephan Beal wrote: > > i might have misunderstood some of the output, but my current understanding > of "correct behaviour," adjusted for the assumption/assertion that the > global config must be writable, is: > > - If the repo is read-only, it must silently fail to remove t

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-31 Thread Stephan Beal
On Sat, May 31, 2014 at 6:49 PM, Stephan Beal wrote: > Am i wrong, or did Joel's patch just correct the problem: > For completeness: [stephan@host:~/tmp/x]$ f-acat rid:3 C egg D 2014-05-31T16:47:37.137 F a 9f2f5f07e9326b68b448f9b452a14f63cfadc27c F b 4e8501912e5755546dd0029fe6f248ac6579f2d7 R 2

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-31 Thread Stephan Beal
On Sat, May 31, 2014 at 4:33 PM, Stephan Beal wrote: > On Sat, May 31, 2014 at 1:21 PM, Richard Hipp wrote: > >> Can somebody please explain to me what this change accomplishes, other >> that introduce needless bugs, which it seems to excel at? What problem >> does it solve? Why shouldn't we b

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-31 Thread Stephan Beal
On Sat, May 31, 2014 at 5:57 PM, Andy Bradford wrote: > Regarding the error, if I understand the R-card, it seems like the > manifest checksum is wrong: > > $ f ci -n -m one file > F file 2464bdd2457e7e5aba5e76138b6bbb31416bc894 > R bd4b079b9dbaf9228c7174fc4675292e > You can actually...

Re: [fossil-users] use of 'fossil close'

2014-05-31 Thread Stephan Beal
On Sat, May 31, 2014 at 6:11 PM, Michai Ramakers wrote: > On 31 May 2014 17:49, Stephan Beal wrote: > > > > On Sat, May 31, 2014 at 5:12 PM, Michai Ramakers > >> I think indeed the 2nd test should close the repo, even if it can't > >> update the config. > > > > i would have expected it to, actu

Re: [fossil-users] use of 'fossil close'

2014-05-31 Thread Michai Ramakers
On 31 May 2014 17:49, Stephan Beal wrote: > > On Sat, May 31, 2014 at 5:12 PM, Michai Ramakers > wrote: >> >> > b) repo is r/w but the global config is read-only >> ... > > Okay, so... Fossil requires that .fossil be > writeable, which means this whole test case is invalid vis-a-vis fossil's > as

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-31 Thread Andy Bradford
Thus said Stephan Beal on Sat, 31 May 2014 16:33:48 +0200: > i would personally like to see it kept (mainly for future > compatibility with libfossil, which doesn't require an initial checkin > ;), but not as the default. The default should stay as it historically > has been - creatin

Re: [fossil-users] use of 'fossil close'

2014-05-31 Thread Stephan Beal
On Sat, May 31, 2014 at 5:12 PM, Michai Ramakers wrote: > ('f.f' is the repo; 'a' and 'b' are initially open roots): > > michai@main:~/fclose$ ls -l > total 136 > drwxr-xr-x 2 michai users512 May 31 16:48 a > drwxr-xr-x 2 michai users512 May 31 16:48 b > -rw-r--r-- 1 michai users 5

Re: [fossil-users] use of 'fossil close'

2014-05-31 Thread Michai Ramakers
On 31 May 2014 17:12, Michai Ramakers wrote: >> >> a) the repo is read-only > > ... for completeness sake: the root at 'a' was closed as per 'fossil stat' after calling 'fossil close' in that dir, when repo was r/o and global config was r/w. Michai ___

Re: [fossil-users] use of 'fossil close'

2014-05-31 Thread Michai Ramakers
On 31 May 2014 16:26, Stephan Beal wrote: > > What happens to 'close' when: > > a) the repo is read-only ('f.f' is the repo; 'a' and 'b' are initially open roots): michai@main:~/fclose$ ls -l total 136 drwxr-xr-x 2 michai users512 May 31 16:48 a drwxr-xr-x 2 michai users512 May 31 16

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-31 Thread Stephan Beal
On Sat, May 31, 2014 at 1:21 PM, Richard Hipp wrote: > Can somebody please explain to me what this change accomplishes, other > that introduce needless bugs, which it seems to excel at? What problem > does it solve? Why shouldn't we back it out? > It doesn't solve a problem so much as open up

Re: [fossil-users] use of 'fossil close'

2014-05-31 Thread Stephan Beal
On Sat, May 31, 2014 at 4:01 PM, Michai Ramakers wrote: > That seems to work fine, thank you. I have merged this branch to trunk > locally, and will continue to use it. If there are any things I can or > should try/test here, let me know. > Great! i'm back from Augsburg but need to run out and d

Re: [fossil-users] use of 'fossil close'

2014-05-31 Thread Michai Ramakers
On 30 May 2014 18:43, Stephan Beal wrote: > On Fri, May 30, 2014 at 2:29 PM, Stephan Beal wrote: >> >> That's likely a misinteraction with the "all" setup and "close." When >> fossil opens a repo db, it automatically records it in the global config db >> for 'all' purposes. The close command "sho

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-31 Thread Richard Hipp
On Fri, May 30, 2014 at 8:14 PM, Andy Bradford wrote: > Looks like this is due to the recent addition of the empty initial > checkin in [cac91b6cd17ab746]: > Can somebody please explain to me what this change accomplishes, other that introduce needless bugs, which it seems to excel at? Wh

Re: [fossil-users] working checkout does not match what would have ended up in the repository

2014-05-31 Thread Michai Ramakers
On 31 May 2014 02:14, Andy Bradford wrote: > Thus said Michai Ramakers on Fri, 30 May 2014 21:06:36 +0200: > >> michai@main:~/proj/081/adm$ f ci -m 'added note about spent time' >> time_spent.txt >> New_Version: 187aa4a7c8b1377ddf05b1d979afe89adeff8dc0 >> working checkout does not match what woul