Thus said Stephan Beal on Sat, 10 Jan 2015 03:56:11 +0100:
> i have an idea but can't try it out:
>
> rebuild_step() local var:
>
> Blob copy;
> ==>
> Blob copy = empty_blob;
Thanks, I'll try it out... I'll have to back up a bit because I already
made a change that will abort on short reads:
Thus said Stephan Beal on Sat, 10 Jan 2015 03:56:11 +0100:
> i have an idea but can't try it out:
>
> rebuild_step() local var:
>
> Blob copy;
> ==>
> Blob copy = empty_blob;
Ok, after many attempts (timing problems are so much fun), I was still
able to get a core dump even after initializi
Thus said Kelly Dean on Sun, 11 Jan 2015 21:37:12 +:
> Just ask your ISP or network administrator to lower your quality of
> service, or try using wifi while a large number of microwave ovens are
> operating nearby.
Wifi with a microwave would have been much easier than what I was doing!
I
Thus said Stephan Beal on Mon, 12 Jan 2015 02:06:30 +0100:
> Seems i can only set "high" and "low" priority, but some boxes may
> allow more details setup.
I can set up all kind of QoS on my firewall, but most devices don't
allow one to request random and routine packet loss and
Thus said Kelly Dean on Tue, 13 Jan 2015 01:42:51 +:
> But if the R-card is optional, then it can simply be removed entirely,
> right?
It can, certainly. That doesn't mean it should in all environments.
Keeping it as an option means that those who are best able to evaluate
the need f
Thus said Stephan Beal on Tue, 13 Jan 2015 03:06:46 +0100:
> [stephan@host:~/cvs/fossil/tcl]$ f-query -e "select sum(b.size) from blob
> b, event e where e.type='ci' and b.rid=e.objid"
> sum(b.size)
> 233986926
Hmm, that number is considerably different than this:
http://core.tcl.tk/tcl/stat
Wh
Thus said Stephan Beal on Tue, 13 Jan 2015 11:51:57 +0100:
> my query above was only counting the size of all manifests.
Oh, that's an interesting query indeed; I must have misunderstood.
Thanks,
Andy
--
TAI64 timestamp: 400054b54e1d
___
fossil-us
Thus said Kelly Dean on Wed, 14 Jan 2015 23:57:57 +:
> Instead of sha1, use something like a 160-bit version of xxhash, which
> is 10-20 times faster than a secure hash, and has no more risk of
> collision than does the latter, assuming you don't commit malicious
> people's data.
The
Thus said Kelly Dean on Tue, 13 Jan 2015 23:24:49 +:
> Yes. And it needs to compare the contents, not just compare hashes as
> a shortcut.
Given Fossil's distributed design, I don't think it is always possible
to compare contents, at least not on the client. For example:
A clones from S
B
Thus said "Andy Bradford" on 15 Jan 2015 13:37:24 -0700:
> Or would the sync protocol have to be modified so that the client, on
> push, receives a copy of any existing artifacts that it is intending
> to push so that it can compare the contents prior to pushing?
Not thi
Thus said Michai Ramakers on Sat, 24 Jan 2015 20:19:20 +0100:
> michai@delle:/tmp/f/f/f2$ ../fossil clone http://fossil-scm.org f.f
> cannot connect to host fossil-scm.org:80
> Clone done, sent: 0 received: 0 ip: 2600:3c00::f03c:91ff:fe96:b959
> server returned an error - clone aborted
Thus said Michai Ramakers on Sat, 24 Jan 2015 21:09:05 +0100:
> > Does your network have IPv6 support?
>
> none whatsoever.
Ok, so apparently Fossil has recently had IPv6 support enabled in the
client and it does seem that it is choosing to use IPv6 in favor of
IPv4, even though you don'
Thus said "Andy Bradford" on 24 Jan 2015 14:00:22 -0700:
> Should Fossil have such a selection mechanism in an option that
> indicates whether IPv6 should be preferred, with the default falling
> to IPv4?
s/in/or/
Should Fossil have such a selection mechanism o
Thus said Richard Hipp on Sat, 24 Jan 2015 16:27:55 -0500:
> I would hope that the local machine knows that it cannot provide IPv6
> service and that getaddrinfo() should therefore always return an IPv4
> address. But apparently that is not happening on Michai's machine.
That's a fair point. I
Thus said Joerg Sonnenberger on Sat, 24 Jan 2015 22:55:31 +0100:
> That's not how it is supposed to work. You are supposed to try the
> entries returned by gai as long as you get unreachable errors. That
> can happen for IPv4 too.
Yes, that is how it *should* work... As far as I know, Fo
Thus said Richard Hipp on Sat, 24 Jan 2015 17:18:18 -0500:
> OK. Enhanced to do as Joerg describes. Seem to work fine on Michai's
> machine now without needing to --ipv4 manually.
Excellent change! After my last email, I started to look at the changes
required and you beat me to it. :-)
Thank
Thus said Steve Bennett on Thu, 29 Jan 2015 09:49:42 +1000:
> This is because (e.g.) http://jim.tcl.tk/index.html/doc/www/www/news/ no
> longer
> automatically redirects to
> http://jim.tcl.tk/index.html/doc/www/www/news/index.html
Likely caused by:
https://www.fossil-scm.org/index.html/info/c
Thus said Jan Danielsson on Sun, 01 Feb 2015 15:08:07 +0100:
> In that thread the commit
> http://www.fossil-scm.org/index.html/info/b4dffdac5e706980d911a0e672526ad461ec0640
> was brought up as a potential fix. I updated to get the fix and then
> tried running a clone, and I could indeed get the
Thus said David Given on Mon, 02 Feb 2015 23:49:55 +0100:
> Judging by the buttons, it's a Pebble:
>
> https://getpebble.com/
Now, if I could get it to run ABClock underneath, I might be in the
market for one:
http://www.let.rug.nl/~kleiweg/abclock/
Andy
--
TAI64 timestamp: 400054d04
Thus said David Given on Mon, 02 Feb 2015 23:51:33 +0100:
> > It seems that doing 'fossil config reset skin' *also* resets the
> > index path to the default.
>
> Does anyone have an opinion on this? I'm not going to do a merge
> without a sign-off...
I don't think it makes much sense
Thus said Richie Adler on Mon, 09 Feb 2015 17:03:13 -0300:
> WARNING: Device "/dev/null" is not available for reading and writing.
>
> WARNING: Device "/dev/urandom" is not available for reading. This
> means that the pseudo-random number generator used by SQLite will be
> poorly seeded.
Thus said Harry Putnam on Mon, 09 Feb 2015 20:03:28 -0500:
> I'm not so concerned about losing my experimental repo recoreds of its
> files. I was trying to ask if I could acquire a much larger set of
> files by moving my current repo db file and then go to the highest
> level of this sp
Thus said Harry Putnam on Mon, 09 Feb 2015 22:32:51 -0500:
> You get the picture. However I've only worked on (part of) one host's
> project files so far and my immediate expansion would be from z up to
> x0 on one hosts files.
How tightly related are the files from different hosts? If they ar
Thus said John Found on Tue, 10 Feb 2015 21:32:09 +0200:
> It doesn't matter. It is even more simple, just detect the first hex
> number, enclosed in square brackets and you will be fine, notice,
> without assuming any length at all. If you want to use finfo with -b
> option, simply scan
Thus said Richard Hipp on Tue, 10 Feb 2015 15:49:06 -0500:
> But I find those 40-character long URL parameters annoying a have been
> slowing reducing the length of (2) in specific places where it annoys
> me. I propose either 16 or 20 as the default length for (2). Probably
> the shorter.
For
Thus said Richard Hipp on Wed, 11 Feb 2015 10:21:32 -0500:
> https://www.fossil-scm.org/skin2
>
> Please let me know if you see any problems with the look of this
> alternative skin.
Looks nice, except it has no background color. Perhaps this is
intentional?
Andy
--
TAI64 ti
Thus said Richard Hipp on Wed, 11 Feb 2015 10:21:32 -0500:
> https://www.fossil-scm.org/skin2
>
> Please let me know if you see any problems with the look of this
> alternative skin.
One other thing I've noticed is that the second-level menu in the
Timeline page doesn't line up
Thus said "j. van den hoff" on Tue, 17 Feb 2015 09:44:47 +0100:
> doing the exact same cloning command after login to the server (i.e.
> via a ssh connection to "itself") the clone is just fine. whether an
> accidental coincidence or not: this happened today and just one day
> after I upda
Thus said "Ashwin Hirschi" on Tue, 17 Feb 2015 21:32:57 +0100:
> Yeah, it feels a bit counter-intuitive: monospaced fonts are usually
> associated with "old things" [;-)]. But using them for the check-in
> links really helps make the timeline easier to read.
I prefer monospaced fonts for mos
Thus said Richard Hipp on Tue, 17 Feb 2015 18:43:15 -0500:
> I have switched the default Fossil repo over to using the San
> Francisco Modern skin. Everybody seems to think it looks a lot better,
> and I agree.
It does look better, but it lacks a background color. :-)
Andy
--
TAI64 ti
Thus said =?koi8-r?B?7cnOxNLP1yDl18fFzsnK?= on Wed, 18 Feb 2015 22:32:02 +0300:
> There's no BASELINE mentioned in Usage header, it's CHECKIN now, so
> I'm sure this is a leftover from the previous version, and probably
> this should be fixed (BASELINE to CHECKIN in the details text).
Thank
Thus said Julie Aguas on Fri, 20 Feb 2015 12:37:02 -0800:
> 1) My source tree is pointing to a branch off the trunk
> 3) I commit the changes to my source tree. I don't request a branch,
> and no message comes indicating that the change will cause a fork. It
> looks like the commit goes throug
Thus said "Andy Bradford" on 20 Feb 2015 15:15:13 -0700:
> Thus said Julie Aguas on Fri, 20 Feb 2015 12:37:02 -0800:
>
> > 5) If I try on another computer which is synced to the same master
> > repository, I see no evidence of the branch existing at all in th
Thus said Oliver Friedrich on Mon, 23 Feb 2015 15:17:35 +:
> Nowmy problemis, ifI connectto arepo via
> http://my.dyn.dns:8080/myrepo I am able to log in as userA. But if I
> do a logout, and try to log in as userB, it always refuses the logon
> and claims tha
Thus said "Gaurav M. Bhandarkar" on Wed, 25 Feb 2015 14:07:08 +0530:
> > if a branch is marked as "closed", it is (by default) hidden
> >
> Oh, I think I understood the significance of unhide. Thanks for
> explaining.
Unless I have missed something, closing a branch does not hide the
Thus said jungle Boogie on Fri, 27 Feb 2015 12:17:15 -0800:
> Can this be updated to check-in as we are graduating from checkin?
This is the first time I've heard anything about ``graduating from
checkin.''
Why?
What purpose can making such a change serve?
Especially where command argum
Thus said Michai Ramakers on Sat, 28 Feb 2015 10:44:59 +0100:
> I'll pick this one up. Did you mean to change the actual option-names
> too?
My vote is to leave checkin without the dash, and after a bit of sed,
Knuth would agree:
lynx --dump http://www-cs-faculty.stanford.edu/~uno/email.html
Thus said Richard Hipp on Wed, 04 Mar 2015 08:13:23 -0500:
> > 2) fossil ignores 'http_proxy' but honors 'proxy' settings if set
> > manually strace shows that fossil hangs on sendto(-1, ...)
>
> I don't understand the problem statement here. And I don't have a
> proxy at hand for testing
Thus said Alexandr Smolnikov on Wed, 04 Mar 2015 18:06:25 +0500:
> 2) fossil ignores 'http_proxy' but honors 'proxy' settings if set
> manually strace shows that fossil hangs on sendto(-1, ...)
>
> All that happened after [32f8da0ce7] check-in
http_proxy appears to be honored just fine for m
Thus said Alexandr Smolnikov on Fri, 06 Mar 2015 09:31:29 +0500:
> > http_proxy appears to be honored just fine for me with [998af5b2a8].
> > Can you provide more details about what is not working?
>
> Maybe it's meaningless now :)
Yeah, unfortunately I sent off my email before I saw your previou
Hello,
There have recently been some changes to make short UUIDs more
prominent, however, I think that new checkins should still display the
full UUID:
$ fossil ci -m test
New_Version: 36eb94ea54
vs
$ fossil ci -m test
New_version: 36eb94ea547e5905b41e6b447efbfd1184311b23
I think I
Thus said "Joe Mistachkin" on Sat, 07 Mar 2015 22:05:48 -0800:
> Personally, I agree. I find having the abbreviated UUID displayed in
> this particular context to be quite disconcerting.
What about some of the other command line checkin contexts that were
changed in [c62e94f8a3]:
$ fossil
Thus said Richard Hipp on Mon, 09 Mar 2015 23:06:59 -0400:
> Which timeline graph do you prefer:
>
> (1) https://www.fossil-scm.org/fossil/timeline?y=ci&nomo=0
> (2) https://www.fossil-scm.org/fossil/timeline?y=ci&nomo=1
(1) because the relationship to the node from which the arrow originates
is
Thus said Richard Hipp on Mon, 09 Mar 2015 23:52:16 -0400:
> Oh, it does. Try a graph with "n=all" and you'll see. When you start
> to get a lot of rails, and the graph gets all scrunched together, then
> (2) is clearly better. The question is should we go with (2) always,
> or use (1) for gra
Thus said Richard Hipp on Wed, 11 Mar 2015 12:48:04 -0400:
> I'm still curious as to how the students managed to get the repo into
> this state, too.
This is possible if you open a repository using the --empty command line
option. Basically, what you end up with when you do this are two DAGs in
Thus said David Mason on Wed, 11 Mar 2015 11:07:11 -0400:
> I have several students who, through some problem while cloning
> the fossil I created for them, created a parallel timeline. (see
> screenshot)
Do you create the intial repository for the students?
If so, do you initializ
Thus said David Mason on Wed, 11 Mar 2015 15:17:57 -0400:
> But I'm back. I could imagine one student doing some weird thing, but
> not a score of them with the same outcome. The directions were as I
> posted (without the bits in red). I would virtually guarantee that
> *none* of the stu
Thus said Richard Hipp on Wed, 11 Mar 2015 15:56:41 -0400:
> That's an processing artifact of the graph generator. The 198f28add5
> check-in references some parent a09a968bf05 which is not in the tree,
> so the graph generator just draws a line off the bottom of the page,
> not knowing what e
Thus said Andy Goth on Wed, 11 Mar 2015 15:56:43 -0500:
> > anonymous does have some privileges not inherited from nobody (hmncz)
>
> anonymous doesn't have z by default.
No, but nobody does:
https://www.fossil-scm.org/index.html/info/68ce0bcf6269988e
Maybe what he really meant was that any u
Thus said Richard Hipp on Wed, 11 Mar 2015 14:32:18 -0400:
> Brainstorming... Maybe something like this occurred:
>
>(1) Copy the original repository file into xyz.fossil
>(2) run "fossil open xyz.fossil"
>(3) Copy a revised version of the repository over top of xyz.fossil
>(4
Thus said David Mason on Wed, 11 Mar 2015 15:17:57 -0400:
> Does that help at all?
I tried these steps with Fossil from trunk and saw the files when I
opened the Fossil. Any chance you could make up a test fossil using
the above mentioned steps (and a fake student/user and TA) in
Thus said Tontyna on Thu, 12 Mar 2015 11:40:32 +0100:
> 1. Created a repo with Fossil 1.30
> 2. Switched to Fossil 1.27
> 3. clone/open worked without warning
> BTW: open produced a _FOSSIL_ but the local reposirory was empty,
> i.e no checked-out files at all
According to David's instr
Thus said Tontyna on Fri, 13 Mar 2015 13:12:25 +0100:
> A tricky SQL statement could probably create the required records...
While no content was lost, the relationship appears to have been lost,
which is why the timeline cannot figure out how to draw it.
Specifically, the problem appears t
Thus said Jan Nijtmans on Fri, 13 Mar 2015 16:28:47 +0100:
> Another way to trigger the 'problem' is using "fossil reconstruct".
> This function reconstructs the repository from artifacts on disk, it
> is very unlikely that the initial empty checkin is encountered as
> first artifact and
Thus said Jan Nijtmans on Fri, 13 Mar 2015 16:28:47 +0100:
> Another way to trigger the 'problem' is using "fossil reconstruct".
> This function reconstructs the repository from artifacts on disk, it
> is very unlikely that the initial empty checkin is encountered as
> first artifact and
Thus said Richard Hipp on Sat, 14 Mar 2015 00:05:07 -0400:
> Am I wrong to think that clicking through the changes in a project
> (not necessarily from the beginning, but from some signification
> event, say the most recent release) in chronological order is
> something that peo
Hello,
I just browsed to:
https://www.fossil-scm.org/fossil/timeline?y=ci
and there is no footer...
Not sure if this is due to the skin that is currently enabled on it, or
some other cause, but I thought I would point it out.
Andy
--
TAI64 timestamp: 40005505086d
__
Thus said "Andy Bradford" on 14 Mar 2015 22:19:22 -0600:
> https://www.fossil-scm.org/fossil/timeline?y=ci
>
> and there is no footer...
Oh, I see the problem. The text in the footer is some color of grey, and
there is no body color defined in www.fossil-scm.org's CSS
Thus said bch on Sun, 15 Mar 2015 01:05:42 -0700:
> Has the Ryerson Bug be characterised?
Yes.
Basically, versions of Fossil 1.27 and older, assumed that the first rid
in the blob table would always be a checkin. This was true because the
first thing fossil new did was to create a bogus check
Thus said Ron W on Mon, 16 Mar 2015 12:21:45 -0400:
> > The requirement, specifically, is that the first artifact that the
> > server sends during a clone, must be a checkin, or older Fossil
> > clients will end up in this state.
>
> Could the server side be modified to insure the first art
Thus said Stephan Beal on Mon, 16 Mar 2015 18:41:34 +0100:
> wiki-/ticket-only repos might not have a manifest at all.
Then these types of repositories would have to be unclonable by older
versions of Fossil. The server would have to refuse the clone request
(similar to how it refuses to ac
Thus said Richie Adler on Mon, 16 Mar 2015 18:53:34 -0300:
> > JavaScript issue?
>
> Disabled NoScript and for more security restarted Firefox with no
> extensions enabled. Same thing.
I wonder if perhaps some cross-site scripting blocking tool is blocking
it?
Andy
--
TAI64 timestamp: 4
Thus said David Mason on Mon, 16 Mar 2015 21:35:51 -0400:
> Does the server fossil know the version number of the client fossil on
> a clone? Or could it ask? If so, it could do what Andy suggests.
Not currently. The client version is not currently exchanged during
cloning. The only piece o
Thus said die.drachen on Wed, 18 Mar 2015 00:58:41
-0400:
> Unfortunately I'm unable to distribute the repo, which is also quite
> large (~730mb .fossil file, >93k commits). Are there additional
> measures I can take to get diagnostic information?
You could ensure that core files are
Thus said Tontyna on Thu, 19 Mar 2015 11:58:40 +0100:
> Starting several fossil servers with "ui" increments port from 8080 onwards.
> Starting several fossil servers with "server" increments port ditto.
> Mixing "ui" and "server" instances results in double-bound ports.
> Don't know whether that'
Thus said Abilio Marques on Thu, 19 Mar 2015 19:22:14 -0430:
> Having said these things, I must confess that in my mind, I find the
> staging area a difference that's not easily solved. Perhaps some of
> you have thought about this before, and have ideas on how to simulate
> it in a clean wa
Thus said Abilio Marques on Thu, 19 Mar 2015 21:08:55 -0430:
> (1) modify a file or files
> (2) add the files (every single time... this sucks sometimes, as Joerg said)
> (3) commit
I'm not sure what (2) is unless you mean that I create new files in the
working checkout and then use ``git add''
Thus said Abilio Marques on Thu, 19 Mar 2015 21:29:28 -0430:
> As a side note, one of the reasons I dislike git is because the
> commands don't do (do as in never) what their name imply, and some are
> hidden as subcommands inside commands that are meant for other
> purposes.
You m
Thus said Abilio Marques on Thu, 19 Mar 2015 21:25:05 -0430:
> By doing git commit -a, your doing an implicit
>
> git add -A before the commit, which stages all the uncommitted
> changes, and then you're working close to what you would in fossil.
I see, this is totally foreign to how I us
Thus said Abilio Marques on Thu, 19 Mar 2015 22:10:41 -0430:
> git commit -a or git commit filename, you're skipping the staging
> area.
Yes, that's right---thanks to your explanation. I haven't needed it and
now that I understand it (at least according what has been discussed)
I'm certa
Thus said Stephan Beal on Fri, 20 Mar 2015 13:45:14 +0100:
> IMO it's inherently evil because it promotes checking in untested
> subsets. Automated tests require a full, valid tree. Checking in a
> part of a change may well lead to code which runs on your machine but
> doesn't run on
Thus said Richard Hipp on Fri, 20 Mar 2015 13:04:44 -0400:
> (1) Make logically separate changes in separate check-outs so that
> they are easy to test and commit separately.
I think this ability to have multiple checkouts of the same repository
is a much more elegant solution, but it does
Thus said Ron W on Fri, 20 Mar 2015 13:19:58 -0400:
> Never too late to stash. If I decide I need to split out changes
> already made, I stash the files, then do "fossil stash gdiff" to
> selectively (re) apply the stashed changes, then build/test/commit.
gdiff allows you to selective
Thus said Abilio Marques on Fri, 20 Mar 2015 13:58:33 -0430:
> Then I start to work in a new feature, and I add 10 functions (I will
> only show one here).
Now that you know about it, can the start of a new feature also involve
another fossil open of the repository for said feature?
Thanks,
A
Thus said Marcel Graf on Fri, 20 Mar 2015 18:30:11 +0100:
> Imho, the "missing piece" would be "stash" having means to do partial
> stashing (finer than on file-by-file base). This the would allow to do
> these "splittings of a mixed up check-outs" a bit easier (including
> testing "before"
Thus said Ron W on Fri, 20 Mar 2015 15:56:51 -0400:
> I've never seen a non-gui, interactive merge, so I don't know how
> feasible to create such a tool
Here's a non-gui, interactive merge (I didn't show it, but there is also
an edit command which invokes $EDITOR on just the chunk in quest
Thus said jungle Boogie on Sat, 21 Mar 2015 12:15:50 -0700:
> Would it be very hard to add the "Older" link to the original URL?:
> https://www.fossil-scm.org/index.html/timeline?u=drh&c=2015-03-21+16%3A42%3A10&nd&n=200
It's actually supposed to be there, but because the number is 101
entr
Thus said jungle Boogie on Sat, 21 Mar 2015 15:47:54 -0700:
> Yes, this is the case for me, too. Didn't think about ui mode!
Will you please give the following change a try:
https://www.fossil-scm.org/index.html/info/ced021fd57ac2bac
It won't work on that website until Fossil is updated there,
Hello,
I'm not sure if I'm the only one bothered by the left alignment of the
buttons in some of the skins...
For example, navigate to:
http://www.fossil-scm.org/index.html/timeline
Then, after clicking Older, the Newer button shows up to the left, thus
causing the Older button to shift to
Thus said Tontyna on Mon, 23 Mar 2015 23:44:18 +0100:
> Reading /www/branching.wiki I stumbled upon the paragraph explainig
> symbolic name tags starting with *sym-* being special.
Maybe some clarification is in order here. This is specifically
referring to the manifest (I think). If
Thus said Ben on Wed, 25 Mar 2015 15:39:12 +0100:
>https://toi...@chiselapp.com/user/toiboi/repository/robot
If you login to the UI on this URL, what Fossil users do you have there?
Iassume at least one of them will be toiboi. This user is the sync user.
> But what exactly *is* the 'toib
Thus said Stephan Beal on Wed, 25 Mar 2015 15:42:26 +0100:
> Something chiselapp-specific, apparently independent of the fossil
> user's name (i would have expected it to set up "toiboi" as the fossil
> user, but i have never used chiselapp).
I believe toiboi is just the sync user that is
Thus said David Mason on Thu, 26 Mar 2015 15:42:41 -0400:
> 5) then commit she got "Unable to write to standard output: The pipe
> is being closed." on the autosync part.
It sounds like something with the SSH connection failed but didn't get
output. Does plink have any debug options that can
Thus said David Mason on Thu, 26 Mar 2015 15:42:41 -0400:
> 6) Subsequent sync does same think - after her command prompt has been
> printed.
Does ``fossil sync'' work?
Also, to get more verbose output from Fossil, you can do:
fossil sync --sshtrace
Thanks,
Andy
--
TAI64 timestamp: 400055
Hello,
While working with some data, I ran into a change in the data that
the sbsdiff doesn't seem to handle very well (either that or my
understanding of how it works is wrong).
If I commit both complete files (file revision 1, followed by file
revision 2), the sbsdiff show
Thus said Richard Hipp on Fri, 27 Mar 2015 05:49:47 -0400:
> Indeed. The heuristic used in this case is probably
> https://www.fossil-scm.org/fossil/artifact/117b008502a5?ln=1005-1013
Yes, that was it. If I increase this number to 100 it handles it
just fine (actually it started working
Thus said "j. van den hoff" on Fri, 27 Mar 2015 14:37:32 +0100:
> In a couple of years using fossil I have never encountered something
> like this. any ideas what might be going on here?
The only time I've seen Fossil due inexplicable things like this is when
I had recently updated and recom
Thus said "j. van den hoff" on Fri, 27 Mar 2015 20:37:37 +0100:
> in any case problem no. 2 is more irritating. I have no idea how
> fossil could accept the checkin locally without propagating the
> checkin to the remote url despite 'autosync on' and without throwing
> an error...
Thus said Joe Knapka on Sat, 28 Mar 2015 09:19:57 -0600:
> I went back to LaptopA and did "fossil update", only to receive the message:
>
> Error: wrong project
>
> Any idea what might be happening here?
This will happen if the sync was attempted against a different Fossil
project. Each Fos
Thus said Joe Knapka on Sat, 28 Mar 2015 09:54:35 -0600:
> Laptop A: 1.32 [5811ecd7cc]
This version has a correction made to it here that you probably need:
http://www.fossil-scm.org/index.html/timeline?c=14b8475598268f3a
Andy
--
TAI64 timestamp: 40005516da62
Thus said Dewey Hylton on Sun, 29 Mar 2015 10:03:29 -0400:
> so ... is there a way to accomplish this without using cgi? am i on
> the right track? what am i missing?
Given that you're using nginx as a proxy, perhaps you need to add
--baseurl to the fossil server options?
Andyk
--
TAI
Thus said Matt Welland on Mon, 30 Mar 2015 21:08:49 -0700:
> +1 circular nodes, +1 colored lines, seemed to make visually tracking
> the branch easier to my eyes. but as Brad said, a matter of style.
Definitely a matter of style. While I think both are pretty, I prefer
black edges (the nodes
Thus said Dewey Hylton on Tue, 31 Mar 2015 09:48:22 -0400:
> ... any other suggestions? i really prefer to stay away from cgi and
> making my own index page ...
I believe --baseurl is what you actually want to use, however, I'm not
sure --baseurl even works. Everytime I've seen someone try to
Thus said Dewey Hylton on Wed, 01 Apr 2015 13:13:23 -0400:
> meanwhile, should we expect this change to be committed to trunk and
> available in the next version?
It looks like it has already been merged. I might still add an extra
condition to be sure this is only used when the reposito
Thus said Oliver Friedrich on Thu, 02 Apr 2015 20:56:38 -:
> As I'm completly new to c programming this is more a draft than
> anything I would call a contribution, but for "fossil server" it works
> already and I'll definetly spend more time on that next week.
Is it isn't necessary to
Thus said Oliver Friedrich on Thu, 02 Apr 2015 20:56:38 -:
> 1. The part on invoking a cgi-server with the zIpAddr parameter
> specified is not tested, since I cannot figure out when this is used.
> However, it zIpAddr is an ipv4 string (e.g. 127.0.0.1) it will be
> converted to
Thus said klaute on Fri, 03 Apr 2015 18:29:32 +0200:
> last days I have written a small script to convert the fossil timeline
> (verbose commandline) to a gource [1] readable output.
That looks interesting. Do you have a demo screenshot of Fossil? :-)
Thank,
Andy
--
TAI64 timestamp: 4000551
Thus said John Found on Sat, 04 Apr 2015 01:25:27 +0300:
> Sorry, I am not git/github user. Feel free to use the code from my
> e-mails, or your own fixes (as I said, my python skills are close to
> zero).
Except, that you correctly point out that if you pass a dictionary into
a function,
Thus said Ron W on Mon, 06 Apr 2015 15:18:56 -0400:
> Auto-sync helps to avoid forks. But the best way to avoid forks is
> good communication between contributors. Still, I would like to see
> the ability to generate a warning when a Fossil server receives a
> commit against a parent t
Thus said Piotr Orzechowski on Tue, 07 Apr 2015 19:46:22 +0200:
> If they can happen when two people push to central repository one
> after another, then IMHO they should be blocked. Or at least there
> should be a possibility to enable/disable some kind of lock mechanism.
I wonder just
701 - 800 of 1046 matches
Mail list logo
