2013/8/2 Andy Bradford
amb-sendok-1377995615.lfipjljlncecmjghe...@bradfords.org:
Does this mean that the merged fork is no longer a leaf at all? If this
is the case, why assign a closed tag to it?
I never tried fossil merge --integrate for merging a fork before, but
it seems to me that
2013/8/2 Jan Nijtmans jan.nijtm...@gmail.com:
2013/8/2 Andy Bradford
amb-sendok-1377995615.lfipjljlncecmjghe...@bradfords.org:
Does this mean that the merged fork is no longer a leaf at all? If this
is the case, why assign a closed tag to it?
...
Using --integrate makes it impossible for the
2013/8/2 Jan Nijtmans jan.nijtm...@gmail.com:
If the merged is not a leaf anymore, due to the commit itself, I
would expect this function to protect from adding a closed tag
(even though it doesn't really harm here).
Hm.
Bug fixed here:
Hi
Sorry if this has been bought up before, I had a brief look, but didn't see
anything obvious.
It seems that 'fossil stash save X' will create empty diffs for files that
are tagged as being merged.
I've attached a shell script that reproduces the problem on OSX with fossil
1.25:
This is
Hello,
I am having trouble with a fossil repository containing many binary files.
Firstly, after cloning I only have the first (empty) commit in the
timeline, even though many commits have been made to the cloned repository:
$ fossil timeline
=== 2013-08-01 ===
13:06:56 [c497b616a3] *CURRENT*
On Fri, Aug 2, 2013 at 5:51 PM, Benedikt Ahrens benedikt.ahr...@gmx.netwrote:
$ fossil version
This is fossil version 1.22 [ab461f39af] 2012-03-29 08:48:38 UTC
Oh, my, that's practically 27 years old. In that time one of the devs
(don't remember who) put a lot of work into trimming down stray
Hi,
I noticed another problem with fossil that's working behind rproxy.
Admin - Log: presents column named IP Adress. This is rproxy IP no clients
IP.
In rproxy configuration (fossil server) fossil should include IP from
X-Forwarded-For http header.
jl
7 matches
Mail list logo
