1. If I say fossil ui and the browser starts successfully and then
exits, Fossil should exit, too. It should arguably exit even if it
fails to start the browser, since you asked for a UI and it couldn't
provide one.
I gather that it behaves the way it currently does because fossil
server
I'm currently working through the conversion of a 14 year old (!) svn
repo to Fossil, and ran into dodgy behavior in one of the iterations.
Over the years, we've changed how we named branches and tags a few
times. We had a mess like this:
mms5_00
mms6.3
mms-7.0
mms-v8
Dash
On 2/20/2013 09:21, Richard Hipp wrote:
In http://www.fossil-scm.org/fossil/info/f4143c5b59 you can add an IP
address to the --port option:
I don't see that that patch touches the parsing of -P in main.c:
iPort = mxPort = atoi(zPort);
It also doesn't change how
On 2/20/2013 07:52, Richard Hipp wrote:
So I just tried it. I type:
sudo /home/drh/bin/fossil server
and it is working fine for me. Browsing to
http://localhost:8080/test_env; confirms that fossil has entered a
chroot jail prior to serving content.
I, too, can get fossil server to run
On 2/20/2013 13:23, Richard Hipp wrote:
On Wed, Feb 20, 2013 at 3:16 PM, Warren Young war...@etr-usa.com
mailto:war...@etr-usa.com wrote:
I don't see that that patch touches the parsing of -P in main.c:
I was referring to the version. The complete patch is a collection of
two different
On 2/20/2013 13:30, Themba Fletcher wrote:
Does the following help in your case?
tif@:~$ fossil help settings | grep main-branch
main-branch The primary branch for the project. Default: trunk
No, sorry.
It makes sense that it doesn't help. If I open the minimal testcase
/remotes/bug@2
mark :2
author Warren Young war...@etr-usa.com 1361393847 +
committer Warren Young war...@etr-usa.com 1361393847 +
data 13
added files
M 100644 :1 c
M 100644 :1 d
commit refs/remotes/bug
mark :3
author Warren Young war...@etr-usa.com 1361393881 +
committer Warren Young war
I've attached an improved version of the Subversion to Fossil script in
the Cookbook: http://www.fossil-scm.org/fossil/wiki?name=Cookbook#SVN
The general mode of operation is the same, but I've made a bunch of
improvements. In rough order of importance:
- The most important change is that
On 2/21/2013 02:03, Martijn Coppoolse wrote:
This sounds as if the 'Files' tab of your repository links to
http://server/repo/dir?ci=tip
whereas you expected it to link to
http://server/repo/dir?ci=trunk
Yep, you've nailed it.
tip is the out-of-the-box default on a fresh repo, and
On 2/22/2013 14:09, Warren Young wrote:
trunk would be a good
default if Fossil had a training wheels mode for newbies like me, but
I can't seriously propose that as a feature.
Thinking more about it, this is really a Subversion issue. Unlike Git
and Fossil, svn lets you create a branch
On 3/1/2013 06:56, Jan Nijtmans wrote:
Cygwin compilation warning when compiling fossil:
./src/sqlite3.c: In function ‘winFullPathname’:
./src/sqlite3.c:34247:5: warning: ‘cygwin_conv_to_win32_path’ is
deprecated (declared at /usr/include/sys/cygwin.h:34)
[-Wdeprecated-declarations]
On 4/3/2013 15:24, Rene wrote:
News or Old News? To me it was new.
~15 months old news:
http://cygwin.com/ml/cygwin-apps/2012-01/msg00054.html
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
On 4/4/2013 11:03, Rene wrote:
(e.g. Redhat users could try cent-os).
Two problems here.
First, there is not *a* Redhat Linux distribution. There is Fedora
and there is Red Hat Enterprise Linux. The distinction matters because
they do not share repositories, and their binary RPMs are
On 7/24/2013 02:33, Jan Nijtmans wrote:
SQLITE_CANTOPEN: os_win.c:34063: (3)
winOpen(/var/tmp/etilqs_FoaHNBQa56cVGrh\etilqs_PXfZEjH5dBl8Cm5) - The
system cannot find the path specified.
I'm not sure whether this is a SQLite 3.7.17 thing or if it is due to
one of the build option changes
On 7/24/2013 05:30, Jan Nijtmans wrote:
It looks like SQLite is doing something wrong here:
http://www.fossil-scm.org/index.html/info/b88edfefbb
That patch is fine on Cygwin as long as you build Fossil with the
external SQLite, rather than the bundled SQLite.
The bundled SQLite is
On 7/25/2013 06:24, Jan Danielsson wrote:
So .. we used the __CYGWIN__ macro to explicitly break fossil on
cygwin? That seems unnecessarily creative to me.
It is well known that the creators of Cygwin do this sort of thing
because They're Just Mean. Maybe Fossil's creators are the same
On 7/25/2013 07:46, Jan Nijtmans wrote:
2013/7/25 Richard Hipp d...@sqlite.org:
If it does work, then I move for the immediate banishment of all __CYGWIN__
macros.
Doing that will break four things:
- Accessing a check-out repository on Cygwin, while the previous check-out
was done in
On 7/25/2013 04:29, Richard Hipp wrote:
Native, pure-blooded windows binaries run just fine on cygwin, right?
Mostly, yes.
There are exceptions. The Windows console infrastructure isn't as
general and as easy to hook into a the Unix TTY equivalent, so there are
programs that only work
On 7/25/2013 16:03, Joe Mistachkin wrote:
Warren Young wrote:
I'm up for some spelunking. Let's go:
What about all the __CYGWIN__ blocks in the following files?
I guess they already got taken out of the trunk. I did my spelunking in
a current pull of the tree.
That explains why
On 7/25/2013 16:52, Joe Mistachkin wrote:
Warren Young wrote:
I guess they already got taken out of the trunk. I did my spelunking in
a current pull of the tree.
I'm simply searching trunk for __CYGWIN__.
I was stuck on a branch from February. wince
Now that I'm actually looking
On 7/24/2013 05:06, Warren Young wrote:
On 7/24/2013 02:33, Jan Nijtmans wrote:
Just wait on the Cygwin64 people to bring out a new Sqlite package with
the same fixes already done in Cygwin32.
Um, it's the same people. Me. :)
Oh, I see what you mean. I forgot that I didn't release 3.7.17
Some of what I wrote was based on wrong assumptions due to being stuck
here on a February branch of Fossil's repo. Now that I've looked at the
__CYGWIN__ blocks in an up-to-date Fossil trunk, I understand your post
better, Jan. Updated commentary inline below.
On 7/25/2013 15:59, Warren
On 7/26/2013 01:15, Jan Nijtmans wrote:
For your other remarks, I suggest that you become a fossil
code committer.
I've yet to step beyond evaluating Fossil for use here. I like its
features and how it works, but I think I'm going to be forced to use git
for interoperability reasons.
On 7/28/2013 13:47, Marc Simpson wrote:
Output: Cross-site request forgery attempt.
That's a browser-specific feature, not something Fossil does. It may be
that Fossil could work differently to avoid triggering this browser
security feature, but ultimately it's a false positive.
What
On 9/9/2013 07:03, Richard Hipp wrote:
I'd like to provide universal binaries for Mac, but (alas) I
don't know how to do that.
Something like:
$ ./configure --disable-dependency-tracking \
CFLAGS='-arch x86_64 -arch i386'
The --disable-dependency-tracking bit is necessary
On 9/11/2013 08:59, John Long wrote:
On Wed, Sep 11, 2013 at 08:49:14AM -0600, Warren Young wrote:
Only 7 months left of MS support: http://goo.gl/dtpQj4
So what?
After the EOL date, XP will quickly start bit rotting. You can predict
the near future by looking at the state of Windows 2000
On 9/11/2013 08:36, Michai Ramakers wrote:
For my information: is WinXP still an 'officially supported' platform?
I realise it's a bit old, but I happen to use fossil on that platform,
occasionally.
Only 7 months left of MS support: http://goo.gl/dtpQj4
After that, no more security patches.
On 1/9/2014 07:31, Richard Hipp wrote:
But I want Fossil to follow the latest SQLite alphas,
So run sqlite.org with Fossil + SQLite alpha. Everyone is free to run
Fossil in any configuration they like.
Please don't ask the rest of the Fossil user community to alpha-test
SQLite for you,
On 1/9/2014 13:17, Richard Hipp wrote:
SQLite alphas are more robust that stables of most other
software projects.
Are you asserting that no data-destroying bugs have ever appeared in a
SQLite alpha?
Yes, I am. Are you aware of any that I missed?
I'll take you at
On 3/20/2014 10:05, Matt Welland wrote:
FWIW, I don't think I have ever used fossil checkout to move to a
different branch or checkout (which is something I do dozens or
hundreds of times on a typical working day). I always use fossil
update (or usually just fossil up). I
Neither the Wiki nor the Schimpf book explain how to set up a Fossil server
behind a reverse proxy, and a lot of the nginx reverse proxy methods given
online don’t work correctly with Fossil.
After a lot of semi-random flailing, I managed to hit on the magic combination,
so I thought I’d post
I had a file called README-Visual-C++.txt in one of my repositories and
wanted to link to the tip version of it from an outside web page. I
discovered the doc URL feature in Fossil, but it didn't work with that
file. Apparently there's some kind of data sanitization going on here
that turns
On 5/27/2014 13:46, Richard Hipp wrote:
If the filename really does contain + symbols, then the URL should
have %2b for each plus.
Sorry, I should have mentioned that I did try that.
This is with the nginx-proxied configuration that I posted here about on
Sunday. I suspect nginx is
On 5/27/2014 14:37, Richard Hipp wrote:
Candidate fix checked into trunk.
I just installed [5d4400400a] and it still doesn't work, regardless of
%2b or not %2b. (That *was* the query, quoth Hamlet after all.)
I get a Document Not Found page back from Fossil, with the body
section being No
On 5/27/2014 17:10, Joe Prostko wrote:
On May 27, 2014 6:58 PM, Warren Young war...@etr-usa.com
mailto:war...@etr-usa.com wrote:
Incidentally, I'm bothering with nginx proxying because the SCGI
method seems to have broken in 1.28. It was working fine on my site
with 1.27 from the Ubuntu
On 5/27/2014 17:41, Richard Hipp wrote:
Is the documentation better now?
Yes, thanks!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
On 5/27/2014 17:48, Warren Young wrote:
On 5/27/2014 17:41, Richard Hipp wrote:
Is the documentation better now?
Yes, thanks!
Ooops, grammar bug:
Add one might want...
Do you mean Additionally, ...?
___
fossil-users mailing list
fossil-users
On May 27, 2014, at 7:55 PM, Joel Bruick j...@joelface.com wrote:
Richard Hipp wrote:
I think that's an HTTP thing. In a URL, spaces are encoded as +.
It's really an HTML form thing [1] that only applies to the query portion of
the URL. In the path component, we technically should be
On 5/28/2014 10:14, Stephan Beal wrote:
So fossil is incorrect to convert + to space if it is before the first
? in the URL.
Interesting question, especially in the face of this case:
/wiki/foo
equivalent to ===
/wiki?name=foo
the first one has no QUERY_STRING but is, internally,
On 5/27/2014 22:58, Scott Robison wrote:
The best I can come up with for a link to a
wiki page (from another wiki page) is something like
[Page](wiki?name=Page) which really seems kinda ugly
You probably want this syntax:
[Page][1]
later, typically at end of doc...
[1]:
On 5/28/2014 11:58, Stephan Beal wrote:
On Wed, May 28, 2014 at 7:51 PM, Warren Young war...@etr-usa.com
mailto:war...@etr-usa.com wrote:
I don't see that there is ambiguity here at all.
Ah, correct. The onus is on the one creating the link to do the escaping.
...which does mean
On 5/29/2014 10:57, Stephan Beal wrote:
after fixing some bits which assumed too much about the signedness of
the (char) data type,
PowerPC does some strange things with char, too. You might have fixed
that in passing.
As a comparison of runtime speeds, here's the results of the core
On 5/30/2014 11:23, Stephan Beal wrote:
a) pi is using an external USB 2.0 drive here because compiling anything
on a SD card is just too pokey.
Rotating media or SSD?
Did you use the same external HDD on the laptop, or did it have an
unfair advantage in its internal drive?
b) These
On 6/4/2014 10:50, Richard Hipp wrote:
The staging area complicates the interface.
Perhaps you will add some of this to the Fossil vs Git wiki page.
(Section 3.4?)
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
On 6/5/2014 01:51, j. van den hoff wrote:
what _is_ missing is the GitHub layer
I wish to do without that layer. I like Fossil the way it is: simple to
use, yet powerful. I like being able to host my Fossil repo on my own
server.
Perhaps you're getting hung up on the fact that I
On 6/5/2014 04:35, Kevin Martin wrote:
2) Get them to email you the clone
My Fossil DB file is currently only 1.4M, but that's only because I
didn't bother importing the previous 10 years of history into it. If I
had chosen to do that, I expect the file would be bigger than the 10-20
MB
On 6/5/2014 07:14, Richard Hipp wrote:
Suppose you had the ability to create a sub-repository
That was the idea, yes.
A sub-repository would not
even be self-complete: It would only contain artifacts for the file
that changed in the check-ins that it contains
I expected that limitation as
On 6/5/2014 09:18, Andy Bradford wrote:
fossil pull subrepo.fossil -R project.fossil
A contribution from an untrusted outsider needs to be checked carefully
before it is committed to the master repo.
___
fossil-users mailing list
On 6/5/2014 11:54, Richard Hipp wrote:
But maybe there should be an open to the fossil submit or fossil
subrepo command (whatever it ends up being called) so that you can
specify either a dependent or an independent subrepository.
Doesn't the outside developer already have a self-contained
On 6/7/2014 03:27, Stephan Beal wrote:
i wanted to
ask if anyone out there is using multiple Fossil users for one physical
user, what their use cases are, and whether or not it's worth the effort.
I'm a Fossil newbie, so there may be some trap I won't run into for
months or years yet, but as
On 6/7/2014 12:32, Richard Hipp wrote:
On Sat, Jun 7, 2014 at 2:03 PM, to...@acm.org mailto:to...@acm.org
wrote:
Some tools (compilers, assemblers, editors) can deal with any type
of line endings so text saved in a different platform is not an
issue. But, this is not a universal
On 6/9/2014 09:41, Stephan Beal wrote:
My only problem with this approach so far is that the identities skew
the by-user report statistics[1] ;).
That's a feature. Wow, 92% of the checkins are by user warren-work, 7%
by warren-home, and 1% by others. I clearly need to thank my boss again
On 6/11/2014 09:33, Stephan Beal wrote:
On Wed, Jun 11, 2014 at 4:09 PM, JR jr...@saintlyreverend.com
mailto:jr...@saintlyreverend.com wrote:
Alternatively, you can add the location of Fossil to your PATH or
the system PATH.
A minor _potential_ caveat: back when i used Windows/DOS
On 6/24/2014 14:12, Andy Goth wrote:
I'm having trouble with each commit taking about 45 seconds in a new
repository I initially populated with 5154 files totaling 425
megabytes. At this point, there are only five or six commits.
Does this happen when committing a new file to the repo, or
On 6/24/2014 14:23, Andy Goth wrote:
On 6/24/2014 3:22 PM, Warren Young wrote:
On 6/24/2014 14:12, Andy Goth wrote:
I'm having trouble with each commit taking about 45 seconds in a
new repository
Does this happen when committing a new file to the repo, or only
when changing an existing
On 6/24/2014 14:27, Richard Hipp wrote:
It might be possible to provide an option to disable this checksum step
for large repos.
Is that step redundant if the repo is stored on a filesystem like ZFS
that does data checksumming?
___
fossil-users
I'm using the latest tip version of Fossil, and am getting this
complaint on checkins:
Autosync: http://me@server:3691/server
Round-trips: 1 Artifacts sent: 0 received: 0
Pull finished with 343 bytes sent, 716 bytes received
vim ../../ci-comment-B545A069E3EC.txt
New_Version:
On 7/18/2014 09:28, Richard Hipp wrote:
Presumably you get the same error when you do fossil sync or fossil
push, right?
Actually, I think I just figured it out:
$ fossil server /museum # where I keep my *.fossils
$ fossil open /museum/repo.fossil
$ fossil sync
fossil help timeline talks about a BASELINE. I've discovered by
playing that it can be an artifact ID, but I assume there has to be more
to it than that, else why use a different term?
Neither the Schimpf book nor fossil help really explain the term. It
doesn't appear on the documentation
On 7/18/2014 12:39, Richard Hipp wrote:
We should updates the timeline help to say check-in instead, as that
will be clearer to most readers, I think.
Sounds good. Baseline appears in the help for
/ci_edit
/doc
/info
/zip
3-way-merge
ci (as --baseline)
On 7/18/2014 13:05, Ron W wrote:
fossil timeline after | perl -n -e print if /tags: .*branchname/;
That only works if your commit messages are so short they don't cause a
line wrap. I use an 80 column terminal window (old timer, me) so it
doesn't take much to cause a wrap. I tried
On 7/18/2014 12:44, Richard Hipp wrote:
http://www.sqlite.org/src/timeline?a=releaset=trunkn=1000
I think clicking the branch from fossil ui then appending a=AFTERSPEC
will work for me:
http://server:port/repo/timeline?r=BRANCHNAMEa=AFTERSPEC
Today I also learned you can say fossil
On 7/20/2014 23:39, Gour wrote:
but I wonder how safe is to operate Fossil repo with checksum checking
off?
It's as safe as inserting *anything* into a SQLite DB without
checksumming all contents of the DB first.
Could this catch problems, in theory? Sure.
If it does, though, all it can
On 7/21/2014 08:53, Warren Young wrote:
If it does, though, all it can tell you is that your local filesystem or
OS or storage subsystem is untrustworthy.
Relevant reads:
http://queue.acm.org/detail.cfm?id=2367378
https://www.sqlite.org/howtocorrupt.html
On 7/22/2014 10:22, Ron W wrote:
Yes, I know that modern versions of Windows
support symlinks, but I was getting eros from the command so I just did
nested check outs instead.
Native symlinks on Windows are a mess.
First, the mklink command has its options in reverse order as compared
to
On 7/22/2014 10:43, Warren Young wrote:
the mklink command has its options in reverse order
I shouldn't say option here. I mean the two path names you have to
give to both mklink and ln:
$ ln source symlink-target
C:\ mklink symlink-target source
On 7/22/2014 08:38, Michai Ramakers wrote:
I was wondering how many of you use 'open --nested' to have nested workdirs?
Thanks to this thread, I became aware of open --nested, and promptly
found a use for it. So thank you. :)
Here's the problem that open --nested solved for us:
We keep
On 7/26/2014 08:53, Eric Rubin-Smith wrote:
* Code review!
Fossil already provides all the code review I think any nimble team
should need: RSS.
1. Set Fossil up as a server. [1]
2. Go to the Timeline page, and add .rss to the end of the URL. [2]
3. Subscribe to that URL in your feed
On 8/3/2014 15:01, Sean Woods wrote:
What is the latest version of Fossil that will run on the 2.6.x line of
Linux kernels?
I regularly run Fossil on CentOS 5, which still ships kernel 2.6.18.
Can't compile off trunk and I don't know why.
We don't know why, either, since you didn't include
On 8/5/2014 18:50, Sean Woods wrote:
I saw that jimsh references glob.tcl, so I removed all my local Tcl/Tk
stuff -- I wasn't really using it -- and rebuilt Fossil clean from tip,
to force it to use jimsh, and it still doesn't happen.
How did you do this? My knowledge of the TCL ecosystem
On 8/6/2014 01:49, Martijn Coppoolse wrote:
On 5-8-2014 23:16, Warren Young wrote:
1. Set Fossil up as a server. [1]
It's not even necessary to set Fossil up as a server; you can also run
`fossil rss`
Nice. Thanks for the tip.
[2] A quick glance at src/rss.c in the Fossil sources says
On 8/6/2014 15:27, Andy Bradford wrote:
Thus said Warren Young on Wed, 06 Aug 2014 12:22:45 -0600:
Out here in the normal software world, I think we are being
presumptuous to use the word engineering. We usually cannot write an
equation to prove our software correct.
The earth
On 8/6/2014 21:00, Andy Bradford wrote:
Thus said B Harder on Wed, 06 Aug 2014 10:41:47 -0700:
Do we have fine-grained control over pulling only specifically rooted
branches?
No, but you can certainly clone the developers clone and inspect his
changes before pulling into your clone
On 8/7/2014 01:26, Stephan Beal wrote:
i'm pretty certain (not 100%) that that's it, but i know we don't use
any Linux-specific calls which might depend on a newer glibc version,
After I posted that, I went out and looked for a list of Linux syscalls
that included the point where they were
On 8/7/2014 14:20, Hajas, Wayne wrote:
every time I try to
use the formatting features, nothing happens.
Wild guess: you're using a fairly recent version of IE on Windows.
You're probably running into Microsoft's brain-dead choice to run all
intranet sites in compatibility mode by default.
On 8/7/2014 14:51, Warren Young wrote:
On 8/7/2014 14:20, Hajas, Wayne wrote:
every time I try to
use the formatting features, nothing happens.
Wild guess: you're using a fairly recent version of IE on Windows.
On re-reading this, I see that my post looks like pure speculation, but
it's
On 8/7/2014 15:09, Warren Young wrote:
you can use a meta tag to do the same thing
Confirmed. If you go to Admin Skins Header, and add this line
somewhere in head, IE8+ will work in standards mode when you point it
at an intranet instance of Fossil:
meta http-equiv=x-ua-compatible
On 8/11/2014 10:18, Stephan Beal wrote:
it turns out
there's an option somewhere in IE which turns off the default to
compatibility mode option,
I mentioned it in one of my posts: Gear Menu Compatibility View
Settings uncheck Display intranet sites in Compatibility View.
Some sites won't
On 8/12/2014 15:48, Warren Young wrote:
I'll test this in IE7, IE9 and IE10 later on today.
In IE7 on Vista, it kinda sorta works. There are multiple HTML
rendering problems in the Fossil UI -- all typical of IE7 -- but the
patch in the previous message allows Ctrl-B/I/U to do what you
On 8/15/2014 07:14, Abilio Marques wrote:
Cloning over ssh seems to be impossible if the user nobody doesn't have
cloning permissions.
I successfully cloned a repo over SSH where Nobody only has read wiki
and read ticket direct permissions, and inherits no other privileges.
I did this with
On 8/15/2014 14:37, Charles Curtit wrote:
Can a server handle fsyncs
from multiple peers at the same time ?
Careful with your terminology. fsync may mean the POSIX syscall
fsync(), but from context, I think you're actually talking about fossil
sync here.
It's doubly confusing because
On 8/18/2014 16:12, Ron W wrote:
I have considered getting a Chrome book as a way to get a very
inexpensive laptop, but this makes it sound like it would only be worth
it to me if I could wipe it and install a decent Linux distro on it.
I'm not aware of any small, well-built, inexpensive
On 8/18/2014 19:39, Eric Rubin-Smith wrote:
warning: Can't read pathname for load map: Input/output error.
Core was generated by `/home/eric/fossil-src-20140612172556/fossil update'.
Program terminated with signal 11, Segmentation fault.
#0 0xb75bffb0 in ?? () from
On 8/19/2014 11:33, Stephan Beal wrote:
A colleague of mine recently reported out-of-the-box success in
encrypting his root partition
Ubuntu's done this in its stock installer since 12.10.
One of the things I trimmed from that already long post is the
observation that booting through BIOS +
On 8/19/2014 11:50, Eric Rubin-Smith wrote:
Try running it under Valgrind.
I ran it under valgrind already and mentioned the results in the OP --
you probably missed that in my wall of text :-).
No, I just stopped reading when I saw the characteristic smashed stack
gdb output. :)
On 8/28/2014 09:23, Scott Robison wrote:
Would there be any interest in adding symlink support to Windows (where
available [Vista later], leaving the text file approach where it is not)?
While Windows Vista+ technically can make symlinks on NTFS, it has
restrictions that make it unworkable
On 8/28/2014 13:34, Thomas Schnurrenberger wrote:
Fossil can be run as a Windows service.
Thanks for the tip!
Please take a look at the 'winsrv' command.
Alas, I do not keep a native Windows binary of fossil.exe on my Windows
boxes. As you can guess from my prior message, I only run
On 8/28/2014 14:32, Ron W wrote:
On Thu, Aug 28, 2014 at 2:01 PM, Warren Young war...@etr-usa.com
mailto:war...@etr-usa.com wrote:
2. If you *are* running as an Administrator user, you can't create
symlinks from a process that isn't Run as Administrator.
If issue #1 is resolved
I've got a link like this from one of my wiki pages:
a href=/repo/doc/trunk/path/to/file.mdFile/a
When the last checkin was on the trunk, this works. When I check
something into one of the branches, though, I get No such document
errors when clicking such links until I check something
On 8/29/2014 09:59, Richard Hipp wrote:
No, it means that it will show the version of /path/to/file.md
http://file.md that is on the current trunk check-in. But you just
said that file doesn't exist.
I think I see what's happening. My branches have two tags on them, the
one I think of as
I was working in Admin - Tickets - Common and realized that the lists
there are just TH1 code. I asked myself, would it work if I changed this:
set type_choices {
Code_Defect
Build_Problem
Documentation
Feature_Request
Incident
}
to this?
set type_choices {
Code Defect
On 9/2/2014 09:00, Dömötör Gulyás wrote:
This is the main issue I have: git does not follow the principle of
least surprise. I'm sure it *can* do everything, if you know all of
the switches and gotchas. But you don't, even if you think you do.
Apparently many advanced git users have their
On 9/1/2014 15:49, Scott Robison wrote:
the reasons I use fossil
have little to do with its distributed nature (though I'm using it more
often that way as time goes by).
A DVCS can be useful even to a lone developer. Several times since
switching from svn to Fossil, I've spent some of my
On 9/2/2014 12:38, Joerg Sonnenberger wrote:
On Tue, Sep 02, 2014 at 12:08:22PM -0600, Warren Young wrote:
On 9/2/2014 09:00, Dömötör Gulyás wrote:
This is the main issue I have: git does not follow the principle of
least surprise.
Linus Torvalds is unique. No one else on the planet has
On 9/2/2014 08:27, Stephan Beal wrote:
On Tue, Sep 2, 2014 at 4:18 PM, sky5w...@gmail.com
mailto:sky5w...@gmail.com wrote:
Will Fossil ever seek to address very large source control?
Fossil's main target is sqlite (it's a cyclic relationship), and in my
humble (but quite fallible) opinion
On 9/2/2014 14:47, Joerg Sonnenberger wrote:
On Tue, Sep 02, 2014 at 02:45:13PM -0600, Warren Young wrote:
Fossil currently wants to do a cryptographically strong checksum on
every version of every graphic file I've ever created on every
checkin. Consequently, a checkin takes several seconds
On 9/2/2014 14:53, Ron W wrote:
On Tue, Sep 2, 2014 at 2:35 PM, Warren Young war...@etr-usa.com
mailto:war...@etr-usa.com wrote:
(This is also why I've been advocating for the uber-patch feature.
My experience with submitting patches (several different projects) has
been (a) each patch
On 9/2/2014 15:07, sky5w...@gmail.com wrote:
If you could flag a file as Keep latest only, that would be less
painless.
That wouldn't work for me. I want the past versions of the image. [*]
The branch I made of the web app three years ago won't run right with
the current bitmaps. The new
On 9/2/2014 15:11, Richard Hipp wrote:
(1) Fossil *does* store binary files as diffs from their predecessor, if
they are sufficiently similar (that is, if the diff is smaller than the
file itself). the problem is that with compressed images, changing a
single pixel can potentially change most
On 9/2/2014 16:07, Ron W wrote:
On Tue, Sep 2, 2014 at 5:09 PM, Warren Young war...@etr-usa.com
mailto:war...@etr-usa.com wrote:
I've been running an open source project for a decade now, so I can
tell you from experience that a lot of patches come in that do
multiple things
1 - 100 of 889 matches
Mail list logo
