Thus said Abilio Marques on Sat, 16 Aug 2014 12:14:09 -0430:
amarques@laptop-01 ~/tmp/resume $ fossil clone
ssh://abiliojr@raspberry1/.fossilrepos/resume.fossil
.resume.fossil
abiliojr@raspberry1's password:
Round-trips: 2 Artifacts sent: 0 received: 0
Error: not authorized to clone
Thus said =?utf-8?q?Petr_Ferdus?= on Fri, 22 Aug 2014 07:29:12 +0200:
The ckout keyword normally only works when you start your server
using the fossil server or fossil ui command line
Perhaps the documentation on this isn't very clear. You can only use the
ckout keyword for an open
Thus said Stephan Beal on Wed, 27 Aug 2014 19:30:53 +0200:
i only discovered the 0 trick by accident, and found myself using it a
lot when creating links for my user's guide.
I think I discovered ?ln= (or just ?ln really) by accident (or at least
intentional discovery) by seeing what would
Thus said Andy Gibbs on Wed, 27 Aug 2014 18:58:21 +0200:
Is there a rationale behind this? Could there be a flag (e.g. -q /
--quiet would work!) that can do an automatic yes at this point?
I'm not sure about the rationale except perhaps it could be ambiguous.
There are potentially other
Thus said Andreas Kupries on Tue, 02 Sep 2014 15:23:33 -0700:
That information is part of a regular pull operation, so if we can
invoke only the steps to get that, without actually sending any
content back, then your new tool knows what the other side has.
Is it as simple as
Thus said Andy Bradford on Wed, 03 Sep 2014 08:39:32 -0600:
Is it as simple as taking the contents referenced in the unsent table
and putting them into a mini Fossil that has just those artifacts (and
perhaps any requisite predecessors).
Excluding any artifacts referenced in the private
Thus said Richard Hipp on Wed, 03 Sep 2014 10:51:10 -0400:
For example, suppose the person wanting to generate the patch had
actually cloned their clone of the repo, and done pushing and pulling
between his two clones. Then the UNSENT table would have been emptied
on both clones
Thus said Philip Bennefall on Wed, 03 Sep 2014 21:50:28 +0200:
Was this a problem that could be said to be on the server side or the
client side?
The problem that was recently corrected was server side.
Did one of you recently make a largish checkin (as in a large number of
artifacts)?
Thus said Philip Bennefall on Sun, 07 Sep 2014 16:46:49 +0200:
fossil tag add testing trunk
But that did not show up in the editor output. The tags I added using
--tag in the commit command show up just fine now though, which is
great.
Is that because the tag is not propagating? Try
Thus said Stephan Beal on Sun, 07 Sep 2014 17:56:37 +0200:
to assume that all tags passed in this way are symbolic tags[1], and
will in fact do non-intuitive things if you try to use: --tag
'*propagating' (with an asterisk in front to make it look like a
propagating tag). IMO
Thus said Stephan Beal on Sun, 07 Sep 2014 17:56:37 +0200:
However, the --tag option appears:
Ooh, we're talking about --tag, not ``fossil tag'' so maybe my previous
comments were off the mark. Your comments were about making --tag
understand things.
Excuse the interference.
Andy
--
Thus said Stephan Beal on Sun, 07 Sep 2014 17:56:37 +0200:
to assume that all tags passed in this way are symbolic tags[1], and
will in fact do non-intuitive things if you try to use: --tag
'*propagating' (with an asterisk in front to make it look like a
propagating tag).
Thus said Philip Bennefall on Sun, 07 Sep 2014 18:40:32 +0200:
So in summary, it seems that non-propagating tags now show up in the
editor output if they are added as part of the commit command but not
if they are added with tag add.
And that is working as designed. A non-propagating tag
Thus said Philip Bennefall on Sun, 07 Sep 2014 19:39:40 +0200:
However, non-propagating tags added with tag add do not show up. So
even though both tags are non-propagating, one of them shows up but
not the other.
fossil tag modifies artifacts *AFTER* they have been created. fossil
Thus said Andy Bradford on 08 Sep 2014 00:09:18 -0600:
fossil tag modifies artifacts *AFTER* they have been created.
Minor technicality... it doesn't modify the artifact per se, it
generates a control file artifact that applies to the artifact.
Andy
--
TAI64 timestamp
Hello,
Is it possible to have login with read-only access to documentation
pages and Wiki but not view the timeline history? Something similar to
how the public pages glob works, but for an authenticated user?
It seems like this should work, but I haven't found the right
Thus said Andy Bradford on 09 Sep 2014 22:22:43 -0600:
It seems like this should work, but I haven't found the right
combination of permissions yet.
As it turns out, this just doesn't seem possible with Fossil currently.
Would there be any interest in something like:
$ f diff
Index
Thus said Stephan Beal on Wed, 10 Sep 2014 08:38:06 +0200:
A separate (doc-specific) repo?
Basically, yeah, but I don't want users to have access to the history of
changes (e.g. no timeline, no diffs, etc...), only Wiki and Embedded
Docs. And I don't want anonymous users---which means I
Thus said Andy Bradford on 10 Sep 2014 00:26:12 -0600:
As it turns out, this just doesn't seem possible with Fossil
currently. Would there be any interest in something like:
Or how about something like this:
$ f diff
Index: src/login.c
Thus said David Mason on Thu, 11 Sep 2014 00:42:09 -0400:
: Daves-MacBook-Retina-784 ; cat .fossil-settings/allow-symlinks
yes
: Daves-MacBook-Retina-784 ; fs ci -m test
New_Version: 240dcb9a36ff5fde1c3bc1ae1e906dbb479b3698
I could be wrong, but I don't think the .fossil-settings apply
Thus said David Mason on Thu, 11 Sep 2014 10:14:02 -0400:
committing .fossil-settings/allow-symlinks first doesn't. This looks
like a bug to me... what is the point of version-able allow-symlinks?
Actually, it does work. The problem isn't with the versionable setting.
There is a bug, but
Thus said Stephan Beal on Wed, 24 Sep 2014 20:16:13 +0200:
This behaviour is just plain weird. On Linux i can't reproduce it with
either 'meld' or 'kompare':
I'm not sure if this is the same behavior that is being discussed, but
try this with the Fossil repo:
fossil up 2d75e87b76
fossil mer
Thus said Joe Knapka on Fri, 26 Sep 2014 23:51:58 -0600:
Yes, the behavior you describe is what I was expecting. However, in my
repository the Downloads links are not there in the check-in
artifact page for anonymous users, even though the Download ZIP
permission is enabled for
Hello,
I like the new characters for the inherited privileges, however, I find
that the R character, and the text that precedes it also being black, to
be not very readable. The R character make Write Wiki look like Write
WikiR to me (except the R is slightly subscripted and also other
Thus said Stephan Beal on Sat, 27 Sep 2014 08:44:27 +0200:
Another alternative might be to wrap the subscripted characters in
parens/braces, e.g. (R), [R], or {R}.
Good suggestion. I think I like [R] and it looks quite nice with both
the CSS and the []:
Thus said Stephan Beal on Sat, 27 Sep 2014 10:16:23 +0200:
Not sure if this is a bug or not, but the [A] subscript isn't used
anywhere.
It is used, just not on the Anonymous user:
http://fossil.bradfords.org:8080/setup_uedit?id=4
This is perhaps because while looking at the Anonymous
Thus said Stephan Beal on Sat, 27 Sep 2014 10:02:50 +0200:
font-family: monospace;
still trying to decide if that is more readable, though. Not yet
convinced.
I tried it and I didn't think it improved anything, and in fact, it made
it slightly more difficult to read the character (at
Thus said Stephan Beal on Sat, 27 Sep 2014 21:30:38 +0200:
http://www.fossil-scm.org/index.html/timeline?r=inherit-priv-mark-sub
Not the most efficient solution, but it should do for any relatively
recent (early-21st-century) browser.
Works for me on Firefox.
Andy
--
TAI64 timestamp:
Thus said Joe Mistachkin on Sat, 27 Sep 2014 14:43:15 -0700:
Works great. I made a couple style tweaks, including adding some CSS
and moving the new elements out one level. I'm not sure if my CSS is
the best choice, please feel free to enhance the styling.
Looks fine here.
I sometimes
Thus said Stephan Beal on Tue, 30 Sep 2014 17:32:06 +0200:
Here's a screenshot showing a partial implementation, with a couple
different placement options. i'm not happy with any of them :/.
I actually did try to update it myself last night but had alignment
issues due to the font on
Thus said Scott Robison on Tue, 30 Sep 2014 10:04:29 -0600:
Sorry for opening this huge can of worms! :)
Haha, don't sweat it. I've actually wished for some improvements to the
permission checkbox page for a while. I've always found it annoying that
the letters are not displayed when
Thus said Gaurav M. Bhandarkar on Wed, 01 Oct 2014 00:55:39 +0530:
Well, I attempted it because
http://www.fossil-scm.org/index.html/doc/tip/www/custom_ticket.wiki
suggested it was possible.
it might be good to automatically scoop up the user's email and put
it here
Access may be
Thus said Stephan Beal on Thu, 02 Oct 2014 19:31:12 +0200:
The weird thing is, he's got two initial empty commits. i'm at a
loss to explain that.
Seems that one of them must have been created with an older fossil and
the other created with a newer version from Fossil's trunk
Thus said B Harder on Thu, 02 Oct 2014 11:17:23 -0700:
Is that even possible? I thought the repo would have to be created
once (and only once), generating it's repo-id, and then cloned for all
subsequent copies before things can begin deviating.
The project-id is stored in a table in a
Thus said David Mason on Thu, 02 Oct 2014 09:35:50 -0400:
I want a script to run every 5 minutes and if there is any update,
email me the update log. But I don't want email every 5 minutes that
just says everything is up to date. I can figure out using file
timestamps etc. if an
Thus said David Mason on Fri, 03 Oct 2014 12:49:17 -0400:
3) It seems like a lot more overhead, compared to a local run of fossil
I'm not sure why you need to parse anything. Here is a low-overhead
script that detects updates to a remote repository:
#!/bin/sh
OLD=$HOME/old.rss
Thus said Stephan Beal on Sat, 04 Oct 2014 21:36:33 +0200:
Before this change autosync_loop() did not consider login-prompt
failure to be an error. This seems to be an unusual corner case, and
i'm not sure which behaviour (old or new) is optimal for this case.
Thanks for tracking this
Thus said Stephan Beal on Sat, 04 Oct 2014 21:36:33 +0200:
If you suspect this change may have unwanted side effects on
other (non-clone) client_sync()-using routines, please voice your
suspicions!
After looking at it, I don't think this introduces any unwanted side
Thus said David Mason on Sun, 05 Oct 2014 11:05:27 -0400:
Absolutely. It should work fine and it's better than my original
shell-only version. I don't really want to do it that way for a couple
of reasons: 1) I don't want to *have* to be running a fossil server (I
do updates via ssh);
Thus said Stephan Beal on Sun, 05 Oct 2014 18:41:33 +0200:
It still seems horribly inefficient, though, considering all the
db-level work it does there, knowing it's going to roll back the
transaction.
Actually, at the moment, there isn't much inefficiency because it's all
local.
Thus said David Mason on Sun, 05 Oct 2014 13:52:45 -0400:
Continuing to think about it, my issue is that I don't want to send
empty emails, an a look at mail(1) suggests that:
fossil update -m | mail -E -s some subject m...@he.re
If you're using the scripted approach, just
Thus said Andy Bradford on 05 Oct 2014 23:18:01 -0600:
On the other hand, the case of fossil update -s seems clear enough,
just run the update and exit non-zero if no updates were made.
By the way, I'm not not necessarily suggesting that this be done. At the
moment, fossil update does exit
Thus said David Mason on Sun, 05 Oct 2014 11:05:27 -0400:
+ if ( statusFlag ) fossil_exit(nUpdate==0);
}
Before you start using this in your own fork, you might want to consider
if having the update_cmd() function exit at this point will cause
problems if FOSSIL_ENABLE_TH1_HOOKS is
Thus said Stephan Beal on Mon, 06 Oct 2014 20:25:55 +0200:
The autosync option provides (incidentally, not specifically by
design) a feature one doesn't have if it is turned off: the ability to
abort a commit within a small (and unknown/varying) time frame.
joke
Perhaps there should be
Thus said Stephan Beal on Mon, 06 Oct 2014 17:23:22 +0200:
http://www.fossil-scm.org/index.html/info/165cc5c093e6ee36a78de5e01f7049235dbc1b1c?ln=1856-1867
Could i convince you to give that look?
Yes, I'll look at it again later. I looked at it briefly before just
long enough to remind
Hello,
In looking at the potential for a ``quiet mode for update'' I wondered
if this might already be possible by simply using TH1 hooks, but then I
realized I don't know much about TH1 hooks except that they can be used
to do things prior to executing a certain command; but what things
Thus said David Mason on Thu, 02 Oct 2014 09:35:50 -0400:
I want a script to run every 5 minutes and if there is any update,
email me the update log. But I don't want email every 5 minutes that
just says everything is up to date.
After thinking about it a bit more, I realized all
Thus said Andy Bradford on 07 Oct 2014 00:21:48 -0600:
fossil sync /dev/null fossil update -n | grep '^changes:' | grep -v
'None. Already up-to-date' {
fossil update 21 | mail -s 'Fossil update' m...@he.re
}
Perhaps something that matches a positive would be better:
fossil sync /dev
Thus said =?UTF-8?Q?Ramon_Rib=C3=B3?= on Fri, 10 Oct 2014 10:01:47 +0200:
If autosync is activated, of course it should do it. In fact, I see it
as an error not doing it. Does not 'autosync' means: do all the pushes
and pulls necessary to keep local repository always syncronized with
remote
Thus said Richard Hipp on Tue, 14 Oct 2014 21:49:47 -0400:
http://cps313.sarg.ryerson.ca/current/Resources/fossil.html
At the bottom of this page is a Last Modified date and by a name we all
should recognize from mailing list traffic. :-)
Andy
--
TAI64 timestamp: 4000543ddd2e
Thus said David Mason on Fri, 10 Oct 2014 09:14:48 -0400:
So the student would do:
fossil clone -A student1 ssh://xxx@remote.machine/student1.fossil
srepo.fossil
Just a quick question regarding this particular setup. Clearly you are
using a shared SSH account in which all your fossils
Thus said David Mason on Tue, 14 Oct 2014 23:27:38 -0400:
If I had my ideal, it would be to have a setting like ssh-clone-id
that could be set (in the remote repo) to -local-, -remote-, or
anything else, and in the anything-else case it would use that.
I had actually considered something
Thus said John Found on Tue, 21 Oct 2014 02:16:20 +0300:
1. Extract all versions tagged with specific tag (for example release).
Use your favorite tool to get:
http://hostname/project/timeline.rss?tag=releasen=99
Assuming you won't have more than 999,999 tagged versions for release
of
Thus said Stephan Beal on Tue, 21 Oct 2014 16:58:28 +0200:
If you don't _really_ need to compare the versions, you can can get
features 1 and 3 in a single step:
http://yourrepo/zip/whatever.zip?uuid=TAGNAME
This is an excellent suggestion if he doesn't really need *all* commits
with a
Thus said Ron W on Tue, 21 Oct 2014 11:41:22 -0400:
Thus said Stephan Beal on Tue, 21 Oct 2014 16:58:28 +0200:
If you don't _really_ need to compare the versions, you can can
get
This is an excellent suggestion if he doesn't really need *all*
commits with a given
Thus said Stephan Beal on Tue, 21 Oct 2014 17:37:03 +0200:
What version does one hope to get from the remote over HTTP? You can
only tell what versions he's copied/pulled (in that it will be at the
top of the RSS feed/timeline), but that doesn't mean he's got that
version checked out
Thus said Stefan Bellon on Thu, 23 Oct 2014 23:49:47 +0200:
What I propose is a consistent and reliable output which doesn't
change when using the same switches specified. I can live with the
current state, however it does not feel right for automated usage.
And that would be the
Thus said Tony Papadimitriou on Mon, 27 Oct 2014 14:18:04 +0200:
I guess the same scenario would be valid if one used a server but had
private branches. My understanding is that private branches do not
sync so the only way to move to another location is to move the whole
fossil file.
Thus said Jungle Boogie on Fri, 31 Oct 2014 09:17:33 -0700:
So the answer is: the side-by-side diff view is the largest and only
image available. You can zoom in on the image via web browser but this
will maximize everything--not just the diff.
I think you can change the font size of the
Thus said jungle Boogie on Sun, 02 Nov 2014 18:03:39 -0800:
Should you expect to see the wiki changes on the cloned copy or will
they always/only be on the project that did fossil init?
Fossil Wiki content synchronizes just like other Fossilized content. If
you have permission to commit
Thus said Richard Hipp on Wed, 26 Nov 2014 18:40:19 -0500:
If you find a repository that gives errors about an incorrect fragment
count, then fix them using:
Thanks, apparently my Fossil fossil had an incorrect fragment count, no
others.
It now reports ok.
Andy
--
TAI64 timestamp:
Thus said K. Fossil user on Sat, 29 Nov 2014 20:55:53 +:
It is strange to me to see my mail in your mailing list response.Is it
not supposed to be hidden ? Even for respect to people privacy ?
If you are referring to the fact that the From header shows your own
email address, it is
Thus said Stephan Beal on Mon, 01 Dec 2014 21:22:56 +0100:
This server could not prove that it is *fossil-scm.org
http://fossil-scm.org*; its security certificate is from *sqlite.org
http://sqlite.org*. This may be caused by a misconfiguration or an
attacker intercepting
Thus said Michael L. Barrow on Thu, 04 Dec 2014 10:44:07 -0800:
~ $ fossil init /tmp/i/test.fossil
project-id: cbabb511a5409961950c5f98d26cae74b49c5fca
server-id: 8c35918cfb451162177d6661eef41c8d8905d75c
admin-user: mlbarrow (initial password is 60d0c7)
So you're trying to pull the config
Thus said Michael L. Barrow on Thu, 04 Dec 2014 13:34:42 -0800:
What I'm trying to do is document the process of creating a new
repository that will be in the same login group of a master repo. From
my understanding, you still need to have the user accounts created in
the secondary
Thus said John P. Rouillard on Fri, 05 Dec 2014 21:38:35 -0500:
Does fossil have a mechanism where I can create and update the tickets
from the command line? Even some form of input format would be useful.
http://www.fossil-scm.org/index.html/help?cmd=ticket
I guess the same question is
Thus said John P. Rouillard on Fri, 05 Dec 2014 21:52:38 -0500:
I am having an issue trying to serve up static files like index.html
with fosssil in server mode. My command line is:
fossil server --files *.txt,*.html /home/rouilj/.fossil_repos
Maybe try quoting the argument following
Thus said to...@acm.org on Sat, 06 Dec 2014 22:23:33 +0200:
One common (for me) example is a text file that includes maybe just
one or two special 8-bit ASCII codes. This causes the whole files to
be stored as binary and makes it impossible to `diff'.
I committed some files with รจ
Thus said to...@acm.org on Sun, 07 Dec 2014 19:55:46 +0200:
I'm not sure about the exact characters that may be causing this as
each file has different ones. (What characters would make the file
binary in fossil's eyes?)
Without actually looking at the source code, I suspect it
Thus said Richard Hipp on Mon, 08 Dec 2014 15:28:30 -0500:
So what is the point of this? Why is the default text/binary detection
not working for Tony?
I looked at the two files he sent as an example, and they had a null
byte (0x00) at the end of the file.
Andy
--
TAI64 timestamp:
Thus said Richard Hipp on Mon, 08 Dec 2014 15:28:30 -0500:
So what is the point of this? Why is the default text/binary detection
not working for Tony?
And more specifically (I didn't know about this command until Stephen
showed it):
$ fossil test-looks-like-utf 9s08gw32.s8p
File
Thus said Ashwin Hirschi on Fri, 12 Dec 2014 00:29:57 +0100:
recently, my team started using Fossil. It took me a while to move our
existing code revisions to Fossil repositories. But it was worth it:
everyone's very pleased with what Fossil offers. So, I'm really glad
we made the jump.
Thus said Ashwin Hirschi on Fri, 12 Dec 2014 01:34:54 +0100:
Good point, but... no, in all cases the end-points where still valid
available afterwards. And if it turned out the commited changes were
not pushed to the remote repository, I could always recover by doing a
fossil sync.
But we
Thus said Ashwin Hirschi on Fri, 12 Dec 2014 01:58:20 +0100:
In other words, for now I'm stuck at browsing the Fossil source code
and hoping maybe someone on the list is able to reproduce the problem.
I've used Fossil with redirected sites before so I may be able to look
at this later, not
Thus said Jungle Boogie on Thu, 11 Dec 2014 17:27:10 -0800:
Any plans to support cloning a specific branch?
While you cannot yet clone a specific branch, you can download the tip
of the source for a specific branch:
http://www.fossil-scm.org/index.html/help?cmd=/zip
For example, to get
Thus said Ashwin Hirschi on Fri, 12 Dec 2014 00:29:57 +0100:
Unfortunately, it looks we've also run into strange crashes related to
(HTTP) redirection. Since many team members work from home, their IP
addresses jump around a lot. To help people find each other, we've set
up a simple
Thus said jungle Boogie on Thu, 11 Dec 2014 21:57:23 -0800:
Interestingly, I had to put quotes around the URL and it downloaded as
zip?name=trunk.zip
Yes, I gave you a bad URL due to a failure on my part to understand the
help. Try:
http://www.fossil-scm.org/index.html/zip/trunk.zip
Same
Thus said Stephen De Gabrielle on Fri, 12 Dec 2014 14:29:28 +:
is it possible to change the submenu links for the tickets page? it
currently has
Edit http://localhost:8080/rptedit?rn=1 New Ticket
You should be able to change this using:
http://localhost:8080/tktsetup_reportlist
Andy
Thus said Jungle Boogie on Fri, 12 Dec 2014 09:37:30 -0800:
This is great. Do you know if there's an rss feed for sqlite?
There is indeed:
http://www.sqlite.org/src/timeline.rss
I think it would be really handy if either project had a visible
location to the rss feed
Yes, more
Thus said Ashwin Hirschi on Fri, 12 Dec 2014 19:16:17 +0100:
It's good to hear Andy may have found the cause of the crashes and has
created a fix.
One detail that I failed to ask... what OS is this on? You mentioned
having a Windows install to deal with, but I wasn't certain if that was
Thus said Ashwin Hirschi on Mon, 15 Dec 2014 19:35:05 +0100:
This would also explain why Andy could not reproduce our exact
problem. My apologies for not mentioning HTTPS earlier, I did not
think it played a part during my initial post.
In any case, does this help track down the
Thus said Richard Hipp on Mon, 15 Dec 2014 21:39:53 -0500:
It should clone fossil. And that appears to work, both before and
after the modifications above.
I was able to reproduce the problem (which only happened with autosync;
triggered by commit), and can confirm that your changes (as
Thus said jungle Boogie on Tue, 16 Dec 2014 13:47:32 -0800:
I'm curious what unhiding here:
https://www.fossil-scm.org/fossil/timeline actually does.
Try it here:
https://www.fossil-scm.org/index.html/timeline?c=2014-11-06+21:46:01
Andy
--
TAI64 timestamp: 40005490ab17
Thus said Sean Woods on Tue, 16 Dec 2014 21:20:51 -0500:
- integers have no prefix
I believe there is an exception for when they represent something that
may be ``boolean'' in which case:
- boolean integers have a b prefix e.g. bBlame
Andy
--
TAI64 timestamp: 40005490ed29
Thus said Stephan Beal on Thu, 18 Dec 2014 20:48:03 +0100:
That infrastructure was only recently added. Over time, more of those
resources will be moved into the file-based system. The build process
bakes those files into the binary, but we could have an intermediate
step for minification
Thus said Stephan Beal on Thu, 18 Dec 2014 21:33:20 +0100:
personally i don't feel that minification would gain us much because
we don't have much css/js, but the points about expiry dates and such
are valid.
Yes, the scope of my question was limited to minification only; I think
the
Thus said Joel Bruick on Sat, 20 Dec 2014 21:51:31 -0500:
Sorry I haven't been able to contribute anything in quite a while, but
this should be fixed on trunk now.
Thanks, the change is much appreciated, especially on high resolution
displays.
Andy
--
TAI64 timestamp: 40005496680c
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 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 or an option
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: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 for
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 use
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 this. This is already what
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 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 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
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 are
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 updated
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 most
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).
Thanks
401 - 500 of 969 matches
Mail list logo
