Thus said Jan Nijtmans on Sun, 18 May 2014 21:34:10 +0200:
I think it would result in the possibility (however unlikely) that a
ticket change hook firing is missing. Scenario: Assume a sync is done
containing 2 chunks, the sync of the second chunk fails for whatever
reason. If the first
Thus said Jan Nijtmans on Sun, 18 May 2014 21:34:10 +0200:
Is there anything else it should do? E.g. should the changes in the
autosync-tries branch be merged with it to make autosync try
multiple times to sync? Perhaps the need to have autosync try harder
is minimized if Fossil
Thus said Matt Welland on Sun, 18 May 2014 22:39:57 -0700:
We are still seeing this scenario. User education seems to have
lessened the frequency a little.
Are you still running a version of Fossil that does not have this fix:
Hello,
I've been using the code for the per-round-trip-commit and while it
seems stable to me, I think it would be good for another pair of eyes to
look at it:
http://www.fossil-scm.org/index.html/vdiff?from=77f53423aec1d2ebto=4cfe13e962a95fe9sbs=1
I think it's ready to merge if folks are
Thus said Stephan Beal on Wed, 14 May 2014 17:47:43 +0200:
'mv' (for reasons ido not understand) sets
vfile.origname=vfile.pathname where vfile.origname IS NULL (that
caused me a bit of greif in libfossil, as i have to work around it in
several places). i
Thus said Matt Welland on Wed, 14 May 2014 16:08:50 -0700:
I have the same annoyance with scrape 'n paste. Would adding a space
between the [ or ] and the hex string alleviate the annoyance but
still provide the visual delineation?
I think the problem isn't the amount of space between
Thus said Jan Nijtmans on Wed, 14 May 2014 12:11:42 +0200:
Anyway, I would like to execute the same plan (merge branch
no-initial-commit to trunk) once more. If anyone thinks this is a
bad idea (maybe because another bug prevents us to do that), I'm all
ears.
I did some
Hello,
I recently noticed that if I hit /stat on my own repositories it shows
``delete mode'' in the Database Stats, but on www.fossil-scm.org it
shows ``wal mode.'' I assume this is to leverage some of the benefits
listed here:
https://www.sqlite.org/draft/wal.html
I suppose it can
Thus said Marty on Tue, 13 May 2014 16:34:29 -0700:
Seems like there's a bug somewhere, but maybe there was an improper
sequence of user events?
Seems like a bug to me.
Here is what I see:
$ fossil merge trunk
MERGE foo.txt
RENAME foo.txt - foobar.txt
fossil undo is available to undo
Thus said Gerald Gutierrez on Sat, 10 May 2014 01:53:56 -0700:
frame #8: 0x000105719ba2 fossil`ssl_receive(NotUsed=unavailable,
pContent=unavailable, N=unavailable) + 50 at http_ssl.c:399
396 size_t got;
397 size_t total = 0;
398 while( N0 ){
- 399 got =
Thus said Stephan Beal on Fri, 09 May 2014 11:16:04 +0200:
So it didn't even attempt to add the file that it said was ADDED.
That's why the R-card is right. The error is the missing F-card.
Please tell me that's not on the trunk?
Yes, it was on trunk, and that's actually how I
Thus said Gerald Gutierrez on Fri, 09 May 2014 15:40:13 -0700:
$ ps auxww | grep fossil
USER PID %CPU %MEM VSZRSS TT STAT STARTED
TIME COMMAND
xxx 7619 0.0 0.2 2490036 29836 ?? S 9:05AM
0:13.80 /usr/local/bin/fossil commit --no-warnings -m
Thus said Jan Nijtmans on Thu, 08 May 2014 12:29:27 +0200:
Well, I went ahead, and merged the proposed change to trunk.
This means that the initial empty commit is no longer created by
surprise, but it's only a change of the default behavior: When
specifying
Thus said Rich Neswold on Thu, 08 May 2014 15:18:43 -0500:
I was thinking of attacking the problem a little higher up (since I'm
way too nervous touching the low-level stuff):
So did I initially, though my first thought was simply to have autosync
try multiple times when failing (in the
Thus said Doug Franklin on Thu, 08 May 2014 23:00:03 -0400:
Does SQLite support nested transactions? If so, that would seem to be
worth considering.
It does appear to support them:
https://www.sqlite.org/lang_transaction.html
Andy
--
TAI64 timestamp: 4000536c46e4
Thus said Rich Neswold on Wed, 16 Apr 2014 15:40:23 -0500:
It would be nice if fossil would break the pull into smaller
transactions which contain valid timeline commits so, if there's a
database timeout, the next time I try to pull it can continue where
it left off.
I've been
Thus said Richard Hipp on Wed, 07 May 2014 07:06:31 -0400:
The purpose of the hooks is to verify that all of the content in the
repository is still accessible. Before each commit, the hooks run to
verify that all of the artifacts can still be un-deltaed and
uncompressed and they
Thus said Richard Hipp on Wed, 07 May 2014 11:02:55 -0400:
We might be talking about different hooks. I'm concerned about the
verify_before_commit hook implemented here:
http://www.fossil-scm.org/fossil/artifact/615e25ed6?ln=94-104
Yes, it does appear that we were talking about
Thus said Andy Bradford on 04 May 2014 22:44:21 -0600:
What have I missed? Perhaps with the per round-trip commit it is not
really necessary to also have a COMMIT if the network drops that is
implemented in [1317331eed]?
Ok, as it turns out, one potential resolution is to simply
Thus said Richard Hipp on Thu, 17 Apr 2014 11:33:59 -0400:
Would that be a valid strategy? Couldn't we end up with a
partial state which we can't work from until the pull finishes to
completion?
The logic (in manifest.c) is designed to be able to deal with partial
state
Thus said Jan Danielsson on Fri, 02 May 2014 17:39:20 +0200:
Artifacts sent: 0 received: 895 Error: Database error: database is locked:
{UPDATE event SET mtime=(SELECT m1 FROM time_fudge WHERE mid=objid) WHERE
objid IN (SELECT mid FROM time_fudge);} #key_3_2
[...]
As you say, it is
Thus said Jan Nijtmans on Thu, 01 May 2014 16:25:18 +0200:
Maybe the idea is good, but the sign of the timezone
correction was wrong, (Just a wild guess! )
I just tested and it's not the sign of the timezone. I created a simple
git repository and then ran through fossil import
Thus said David Given on Thu, 01 May 2014 23:01:50 +0100:
Are you sure that get merged? I remember asking for a sign-off a
couple of times, but never got a response, and eventually abandoned
it.
It actually did get merged:
Thus said Paulus Tuerah on Fri, 25 Apr 2014 06:12:31 -0700:
I'm confused, I clone with user_b and push with user_b, how can
the remote repository use user_a as the committer?
The user that is used to do the sync operation may or may not be the
same user that made the commit in the
Thus said Matt Welland on Tue, 22 Apr 2014 22:22:16 -0700:
This has happened enough that I'm sure it was a real issue but it has
been long enough since anyone reported it to me that I'd assumed it
was fixed.
Unfortunately, nobody has been able to reproduce so it's kind of hard to
fix. The
Thus said Eduardo Morras on Wed, 23 Apr 2014 08:49:52 +0200:
Don't know, but strlcpy() exists only in *BSD libc, but no in
GNU/Linux glibc or Windows.
Sure enough, guess I should RTFM a bit more. I looks like this isn't
exactly an option then, and the strlcpy() that are used in
Thus said Richard Hipp on Wed, 23 Apr 2014 14:19:44 -0400:
QUESTION: What do I call the hyperlink that shows annotate/blame
only forwards in time instead of backwards in time.
Could it be considered commit trail?
Andy
--
TAI64 timestamp: 40005358400e
Thus said Michai Ramakers on Wed, 23 Apr 2014 18:34:32 +0200:
I have no clue on sync logic at all, but perhaps this helps: in all
cases I remember here (3 or so), when sync of commit on host A was not
seen during sync on host B, doing a dummy-commit on host A, then
pulling again on
Thus said Samuel Debionne on Tue, 22 Apr 2014 11:36:46 +0200:
Here is a sequence I'm doing several times a day for years and that did
not work this morning :
fossil commit -m Blabla from my PC
fossil update from my Mac
Has a fork happened? Have a look at the timeline
Hello,
As of [2aaae64a59] compiling Fossil on OpenBSD results in a warning:
bld/name.o(.text+0x11a): In function `test_ambiguous_cmd':
./src/name.c:742: warning: strcpy() is almost always misused, please use
strlcpy()
Is this something to be concerned about for Fossil? I know there are
Thus said Stephan Beal on Tue, 22 Apr 2014 18:07:08 +0200:
Just to confirm that: this has come up several times before in the
past year and, so far, has remained unexplained. We're not sure what
causes it or how to reproduce it. (At least i don't remember seeing
any commits/posts
Thus said Matt Welland on Wed, 16 Apr 2014 09:01:28 -0700:
Autosync: ssh://host/path/project.fossil
Round-trips: 1 Artifacts sent: 0 received: 0
Error: Database error: database is locked: {UPDATE event SET mtime=(SELECT
m1 FROM time_fudge WHERE mid=objid) WHERE objid IN (SELECT mid FROM
Thus said Matt Welland on Mon, 21 Apr 2014 09:26:25 -0700:
Yes! This is fixed on latest! Any idea which commit fixes the problem?
Will you tell me exactly which version of fossil it is? e.g. run
``fossil version'' with the fossil binary that exhibits the problem on
the server.
Thus said Matt Welland on Mon, 21 Apr 2014 09:26:25 -0700:
Yes! This is fixed on latest! Any idea which commit fixes the problem?
I ran fossil bisect to figure out where the fix came into trunk [I must
say, this is the first time I've used fossil bisect and it was quite
handy!]. Here is
Thus said Richard Hipp on Thu, 17 Apr 2014 11:13:38 -0400:
Would this really require a big change? Seems like about all you have
to do is COMMIT after each round-trip to the server, rather than
waiting to COMMIT at the very end. Or, just COMMIT instead of ROLLBACK
after getting a
Thus said Andy Goth on Sat, 19 Apr 2014 16:38:44 -0500:
$ fossil http
GET /timeline
Works for me:
$ ../fossil http
GET /timeline
...
This page was generated in about
0.011s by
Fossil version [53aea235fa] 2014-04-15 09:40:49
/div
/body/html
Also works for HTTP/1.1. I see we're using the
Thus said Andy Goth on Sat, 19 Apr 2014 17:12:04 -0500:
Well, I do have $SSH_CONNECTION set due to having logged in via ssh.
Yes, and ``fossil http'' reads that variable to determine what IP
address the SSH client is coming from. Perhaps there is a better way or
at least there might be
Thus said Matt Welland on Wed, 16 Apr 2014 09:01:28 -0700:
fossil commit cfgdat tests -m Added another drc test
Autosync: ssh://host/path/project.fossil
Round-trips: 1 Artifacts sent: 0 received: 0
Error: Database error: database is locked: {UPDATE event SET mtime=(SELECT
m1 FROM
Thus said Matt Welland on Fri, 18 Apr 2014 08:52:09 -0700:
Round-trips: 1 Artifacts sent: 0 received: 0 Round-trips: 1
Artifacts sent: 0 received: 109 Round-trips: 2
Artifacts sent: 0 received: 109 Round-trips: 2
Artifacts sent: 0 received: 773 Round-trips: 3
Artifacts sent: 0 received: 773
Thus said Matt Welland on Fri, 18 Apr 2014 10:32:26 -0700:
Could it be an OS dependency? I'm on SuSe Linux (SLES11).
No, I can reproduce it on OpenBSD. I'm looking at it more closely to see
what might be causing it. Basically, you need a long commit in progress
and then try to sync. I can
Thus said Matt Welland on Fri, 18 Apr 2014 10:41:39 -0700:
How big is the repo? The one I'm cloning is 420 MB. Perhaps that is a
factor?
No, the problem appears to be the difference between using test-http and
http as the remote command. The default behavior for the Fossil client
is to send
Thus said Andy Bradford on 18 Apr 2014 18:56:09 -0600:
Everything works as expected (e.g. no locking issues).
I spoke too soon. If I give the Fossil user permissions (e.g. don't
clone as nobody) then the issue arises again.
It doesn't appear to be isolated to just SSH. I can cause
Thus said David Given on Mon, 14 Apr 2014 22:28:07 +0100:
It might also be useful to add:
# (To abort the commit, leave this file unchanged)
I was about to point out that this wouldn't be a good idea when using
merge --cherrypick because it actually automatically includes the
Thus said Andy Bradford on Mon, 14 Apr 2014 21:40:00 -0600:
... but apparently Fossil is smart enough to figure out that even with
an uncommented line in the commit message, it still treats it as an
empty message unless you alter it!
Correction, unchanged, not empty.
Andy
--
TAI64
Thus said Stephan Beal on Sun, 13 Apr 2014 17:54:49 +0200:
question: would this need fixing?
I think at the very least it should be possible to unset a user that was
configured as a default via ``fossil user default user''; perhaps a
``fossil user undefault'' which executes:
DELETE FROM
Thus said j. van den hoff on Sun, 13 Apr 2014 18:37:56 +0200:
only after your and stephan's responses I realize that `default-user'
is _not_ initialized at the time of repo creation/opening but indeed
only via `fossil user default somename'.
It is correct that when you first clone, Fossil
Thus said Stephan Beal on Thu, 10 Apr 2014 15:51:31 +0200:
IIRC the original problem was that the user name was not being
remember for normal use cases. That particular change has been in
place since October with no problem reports except for this corner
case (i didn't even
Hello,
It isn't possible to do fossil sync/pull/push --once anymore after
cloning a repository if the Fossil user does not match the local user
due to this change:
http://www.fossil-scm.org/index.html/info/64aa75260f48781c
This is what happens...
Here, the new URL is properly parsed
Thus said Stephan Beal on Tue, 08 Apr 2014 16:58:00 +0200:
AFAIR the point of collisions with Events has never been
mentioned/pointed out before. i, for one, would be all for the UUID
resolution treating events equally, _but_ that opens up potential new
UUID ambiguities
Thus said Andy Goth on Mon, 07 Apr 2014 14:33:10 -0500:
Those look fine, but did you really intend to reject all requests for
UUID abbreviations shorter than four characters?
Yes, it was intentional. It was not my intention to change the length at
which short UUIDs were supported, only to
Thus said Andy Bradford on 07 Apr 2014 19:59:33 -0600:
It's possible that one of these will collide with a ticket, ticket
change or other blobs... Should these also be subject to the same
test?
By the way, in the event that there is a collision, the blob is
preferred over
Thus said Andy Goth on Mon, 07 Apr 2014 22:43:21 -0500:
I do prefer consistency, but we're going to need to think more about
whether we want to break something which used to work just for the
sake of consistency.
I'm leaning more towards the thought that this didn't really work well
Thus said Kai Lauterbach on Sun, 06 Apr 2014 12:52:24 +0200:
klaute@dev:AmbiControllerRemote$ fossil push
http://klaute:password@pi:8193;
Round-trips: 2 Artifacts sent: 4 received: 0
Push finished with 5629 bytes sent, 606 bytes received
This should have prompted you to remember the
Thus said Martin Gagnon on Sat, 05 Apr 2014 10:55:58 -0400:
http://www.fossil-scm.org/index.html/timeline?y=ci
The checkin from 2014-04-04 10:20 get a merge that look to come from
nowhere. (I've tried to follow the line with n=2000)
It looks normal to me. Specifically it looks like
Thus said Andy Goth on Thu, 03 Apr 2014 13:07:44 -0500:
Thus said Andy Goth on Wed, 02 Apr 2014 21:37:35 -0500:
When the UUID is abbreviated to one or two characters, the
ambiguous artifact page is bypassed, and it always seems to link to
a ticket.
Thus said Jan Nijtmans on Thu, 03 Apr 2014 09:06:30 +0200:
Fixed here:
www.fossil-scm.org/index.html/info/c23190a61d
Looks good!
Thanks,
Andy
--
TAI64 timestamp: 4000533d73db
___
fossil-users mailing list
Thus said Andy Goth on Wed, 02 Apr 2014 18:05:24 -0500:
The highlighting in most lines of this diff is confusing, and I don't
think I can explain it fully. You'll just have to see for yourself.
Indeed, there are numerous cases of something being highlighted as a
change even though it's
Thus said Andy Goth on Wed, 02 Apr 2014 20:52:04 -0500:
For unified and side-by-side diffs, I'd like the option to show the
entire file in addition to the current behavior of showing only a
limited context surrounding the changes.
Maybe I misunderstand your intention, but while
Thus said Andy Goth on Wed, 02 Apr 2014 21:37:35 -0500:
When the UUID is abbreviated to three characters, no artifact is
found.
When the UUID is abbreviated to one or two characters, the ambiguous
artifact page is bypassed, and it always seems to link to a ticket.
This explains part
Thus said Andy Goth on Wed, 02 Apr 2014 21:37:35 -0500:
When the UUID is abbreviated to one or two characters, the ambiguous
artifact page is bypassed, and it always seems to link to a ticket.
This explains why it always links to a ticket once you get to ``4e'' and
just ``4'' for the UUID:
Thus said Andreas Kupries on Mon, 31 Mar 2014 08:48:16 -0700:
That should be configurable in the HTML setup of the view page, i.e.
repo/tktsetup_viewpage
Generally look at
repo/tktsetup
Thanks, I'll take a look at these pages and see if I can get them to
work out.
Andy
--
Hello,
Some of the tickets I submit have long lines in them, mainly due to
base64 encoded data. In these tickets, the summary ends up far to the
right of the browser and require scrolling to see. I don't mind the long
lines in the comment, but is there any way to keep the summary in
Thus said Mallik Abhinas on Wed, 26 Mar 2014 16:25:17 -:
And I want it to be changed to 80, I want my website to run in 80 port
not on 8080.
You should be able to get some ideas about how to set this up from the
following:
http://www.fossil-scm.org/index.html/doc/trunk/www/server.wiki
Thus said Andy Goth on Mon, 24 Mar 2014 17:14:58 -0500:
At present, the only way to distinguish between files and directories in
flat view is to check whether their link URL goes to dir or finfo.
Will this work?
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg13816.html
Thus said Michael Weise on Fri, 14 Mar 2014 11:03:20 +0100:
Doesn't fossil store the password for future use?
fossil version?
Andy
--
TAI64 timestamp: 4000532314e6
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
Thus said Richard Hipp on Tue, 11 Mar 2014 10:32:23 -0400:
I think I've seen this too. It might be a bug in fossil stash.
It does appear to be so, however, I'm not certain what the best fix is.
How about:
http://www.fossil-scm.org/index.html/info/c2d748ae2c
Or would it be better just to make
Hello,
Is there any interest in testing and merging in the changes I made on
the http-auth branch?
It's fairly functional at the moment and as far as I know there are not
any problems.
The changes include:
1) Automatically prompt for HTTP Basic Auth when receiving a 401 in a
Thus said Ron Aaron on Thu, 06 Mar 2014 06:48:45 +0200:
Does this mean something to someone? It's as though stunnel is trying
to set a socket option on stdout or something... any help with this
would be appreciated, I'm surely not the only person with this issue.
Can you share your
Thus said Ron Aaron on Thu, 06 Mar 2014 16:54:41 +0200:
The attached zip has the conf file as well as the log.
The stunnel.conf that you sent worked just fine for me. I was able to
successfully clone. At what point in your setup do you see the stunnel
errors? What version of stunnel?
Thus said Jan Nijtmans on Wed, 05 Mar 2014 10:08:00 +0100:
Sorry, I respectfully disagree. Changing Listening to listening is
a real change inside the string, indentation (sol-whitespace) and
eol-whitespace (such as \r preceding \n) is generally considered
irrelevant for
Thus said Jan Nijtmans on Wed, 05 Mar 2014 22:52:04 +0100:
Happy continued testing.
I've been testing on the diff-eolws branch and it all looks and works
very nice. Thanks for fixing the button that I introduced and didn't
realize it didn't honor the Show Log button.
Andy
--
TAI64
Thus said Jan Nijtmans on Tue, 04 Mar 2014 09:20:28 +0100:
That said, I would prefer too the default being NOT to ignore
whitespace, that's what most other SCM's do. Except for annotations,
then it is useful to ignore all whitespacing.
Why is it useful to ignore all whitespace
Thus said Jan Nijtmans on Wed, 05 Mar 2014 07:38:05 +0100:
All joel did was remove an if() around those lines, thereby changing
the indent. Does that make joel the author? I think not! The
diff-eolws branch gives the correct answer. Your addition gives the
correct answer after
Thus said Joel Bruick on Mon, 03 Mar 2014 20:42:08 -0500:
Thanks for all the enhancements, Jan. One thing I want to argue,
though, is that diff --tk shouldn't ignore whitespace by default.
I would further argue that the web UI also should not ignore whitespace
by default.
The first
Hello,
I was perusing the recent commits and noticed that the web UI does not
highlight (in red) the actual changes here:
http://www.fossil-scm.org/index.html/info/3df526ca41
On the other hand, fossil diff --tk does actually work correctly:
fossil diff --tk --from 81162e791f --to 3df526ca41
Thus said Stephan Beal on Fri, 28 Feb 2014 11:54:02 +0100:
i understand that i'm in the minority here, but i literally would not
notice if addremove/clean were removed as features, and if the whole
ignore glob stuff went away.
Not that this matters, but I'm in the same camp---I
Thus said Mark Janssen on Thu, 13 Feb 2014 22:06:49 +0100:
* Email verification to prevent spam.
MLMs (mailing list managers; like ezmlm, mailman, etc...) already solve
this problem. Perhaps those who want notifications can subscribe to a
tic...@domain.dom mailing list and the ticket hook
Thus said Baptiste Daroussin on Wed, 12 Feb 2014 08:40:37 +0100:
I have also stolen long ago the google code like theme and has
adapted it a bit:
Is it intentional for all these ``google code'' look alikes to leave out
a background color?
Andy
--
TAI64 timestamp: 400052fc4dbf
Thus said Ron Wilson on Fri, 27 Dec 2013 16:30:43 -0500:
I don't know how Fossil's SSH support works, but I'd be surprised if
it doesn't support use of SSH-Agent.
The nice thing about ssh-agent is that Fossil doesn't need to support
it. As long as Fossil supports SSH, ssh-agent comes for
Thus said Kevin Martin on Sat, 01 Feb 2014 09:14:20 +:
How does fossil authenticate with a server, does it send the password
plaintext? HTTP Basic Auth does!
It's not encrypted, no, only base64 encoded.
I'm not sure whether this should just happen by default unless the
connection
Thus said Matt Welland on Sat, 01 Feb 2014 08:52:56 -0700:
In my opinion fossil should prompt the user for username/password as
appropriate on receipt of a 401. If the channel is not ssl then a
warning/are you sure would be a good idea.
Would the username/password for this
Thus said Andy Bradford on 01 Feb 2014 10:04:23 -0700:
Thus said Kevin Martin on Sat, 01 Feb 2014 09:14:20 +:
How does fossil authenticate with a server, does it send the
password plaintext? HTTP Basic Auth does!
It's not encrypted, no, only base64 encoded.
It seems I
Thus said Kevin Martin on Sat, 01 Feb 2014 09:14:20 +:
I'm not sure whether this should just happen by default unless the
connection is HTTPS as defaulting to sending plaintext auth data over
HTTP seems like a bad idea.
Agreed. It should not happen automatically when the data will
Thus said Tal Yardeni on Wed, 29 Jan 2014 08:31:09 -0700:
I think fossil should automatically detect the 401 and respond
accordingly.
This turned out to be much simpler than I initially thought... I have
just committed a change that makes Fossil automatically resend the
Thus said Ron Wilson on Thu, 30 Jan 2014 16:57:58 -0500:
What part seems to be the problems?
I'm not sure there is a problem, but there have been some
suggestions/questions about how Fossil could handle disparate usernames
(e.g. the HTTP Authenticated user is not the same
Thus said Kevin Martin on Wed, 29 Jan 2014 09:50:05 +:
I don't quite understand this, does it use basic authentication
instead of fossil authentication? How does the fossil server process
know which user you are?
Currently Fossil inspects the REMOTE_USER environment variable
Thus said Kevin Martin on Wed, 29 Jan 2014 09:50:05 +:
I don't quite understand this, does it use basic authentication
instead of fossil authentication? How does the fossil server process
know which user you are?
I realize that my last response to these questions was
Thus said Tal Yardeni on Tue, 28 Jan 2014 14:46:29 -0700:
password for username:
fossil: server says: 401 Authorization Required
It seems that Basic HTTP Authorization is somewhat of a hidden feature.
When it prompts you for your password, you must prepend # to the
password to signal
Hello,
I've just started a branch for exploring a different way to enable the
use of HTTP Authorization headers in requests:
http://www.fossil-scm.org/index.html/info/e747041a72
Of course, removing the special character as a flag to enable HTTP Auth
could potentially break some users who
Thus said j. van den hoff on Fri, 24 Jan 2014 21:25:38 +0100:
I believe you, naturally. I'm only at a loss why, then, once upon a
time I could branch without getting asked for the passphrase. also, I
would expect that someone else would have run into this problem
(clearsign off,
Thus said Stephan Beal on Wed, 22 Jan 2014 19:53:12 +0100:
here's a call for review/suggestions for the vdiff-subdir branch,
based on a suggestion by Michai Ramakers for a subdirectory-based
filter for the /vdiff page, which then mutated into a more generic
glob option.
I gave
Thus said Richard Hipp on Thu, 16 Jan 2014 10:48:06 -0500:
So we have a branch-1.28 which is suppose to be for release. I'm
wondering if anybody is actually using and testing it?
I've been using it since it was branched, although my limited use cannot
come close to that of fossil-scm.org.
Thus said Jan Nijtmans on Tue, 14 Jan 2014 10:33:57 +0100:
And the last one which doesn't affect fossil
at all because fossil doesn't use fork():
https://www.mail-archive.com/sqlite-users@sqlite.org/msg81284.html
Technically it does use fork() for SSH sync operations but I don't
Thus said Pierluigi Moschetti on Tue, 14 Jan 2014 10:01:18 +0100:
I get the message: cannot commit against a closed leaf. Is there a
way to re-open the leaf? I tried to edit the item in the timeline
where Closed-leaf is shown, but I did not find any command to set
the leaf to open
Hello,
While attempting to pull the Fossil repository, I saw this error:
$ fossil up
Autosync: https://www.fossil-scm.org/
Round-trips: 2 Artifacts sent: 0 received: 0
Error: Database error: database is locked: {UPDATE event SET mtime=(SELECT m1
FROM time_fudge WHERE mid=objid) WHERE objid
Thus said B Harder on Tue, 14 Jan 2014 19:38:55 -0800:
No pending commits in other windows? (ie: waiting for you to enter
password for gpg key) ?
No, and in fact, this was the first time I ran any fossil command after
logging in and ps did not show any other fossil commands.
I wonder if
Thus said Sergei Gavrikov on Fri, 10 Jan 2014 19:56:54 +0300:
* Failures: ... th1-setting-5 th1-setting-6
These two failures appear to be happening because they expect to find a
setting (autosync == 1), but find something else. I believe this is
because they operate on the current
Thus said shtine on Wed, 08 Jan 2014 17:02:16 +0200:
/kk1# fossil add ../opt1/one.txt
filename contains illegal characters: /one.txt
Perhaps the error is a bit misleading... Should it be possible to add
files that are above the root of the open fossil repository?
Main question for me is:
Thus said shtine on Wed, 08 Jan 2014 17:02:16 +0200:
if I change the name of the directory, I don't get error, but the name
of file is transformed:
/test1# fossil add ../opt1/one.txt
ADDED ne.txt
Both apparently are bugs. The problem is that all the checks for whether
or not the file
Thus said Joel Bruick on Mon, 06 Jan 2014 18:50:57 -0500:
And... done. For added convenience, you can also expand/collapse every
subdirectory at once by clicking the root directory.
I wonder if it would be a good idea to change the class for tree-view
directories from ``dir'' to ``treedir''
701 - 800 of 969 matches
Mail list logo
