Thus said Donny Ward on Sat, 21 Jun 2014 17:29:07 -0700:
I have two versions of my repository that I've saved from a while ago,
the last time I ran into this syncing issue. I've linked them both
here, hoping that someone can analyze them and figure out what the
issue is.
Indeed it
On 22 June 2014 08:37, Andy Bradford amb-fos...@bradfords.org wrote:
Thus said Donny Ward on Sat, 21 Jun 2014 17:29:07 -0700:
...
Then look at the http-* files that appear:
$ grep gimme http-request-* | random 100
http-request-2.txt:gimme 3621fa11299ea8ab263e754cec37690d4581f660
Thus said Michai Ramakers on Sun, 22 Jun 2014 10:44:05 +0200:
It looks like at least this random selection are all files that were
part of checkin a9b1344817, perhaps all of them are.
Thanks both for putting in time pinpointing this. This is probably no
news: diffing the complete
On Sun, Jun 22, 2014 at 1:18 AM, Michai Ramakers m.ramak...@gmail.com
wrote:
On host A, somehow the remote-url of the local repo was pointing
(using 'file:///...') to itself, causing sync to fail. This is no
surprise really.
Vague suspicion: maybe someone tried to clone it on top of itself
On 22 June 2014 19:02, Stephan Beal sgb...@googlemail.com wrote:
On Sun, Jun 22, 2014 at 1:18 AM, Michai Ramakers m.ramak...@gmail.com
wrote:
On host A, somehow the remote-url of the local repo was pointing
(using 'file:///...') to itself, causing sync to fail. This is no
surprise really.
On Sat, Jun 21, 2014 at 1:06 PM, Michai Ramakers m.ramak...@gmail.com
wrote:
On 21 June 2014 18:48, Michai Ramakers m.ramak...@gmail.com wrote:
does it make sense to have 2 repos on different machines having each
others remote-url?
rephrase: ... having each other as remote-url (i.e. repo
Hello,
Something else I found while compiling Fossil on Haiku. It should be
the last issue I'm having.
I admit I didn't notice it before 1.29 came out, but essentially this
commit caused me some problems:
http://fossil-scm.org/index.html/info/48f1239eb2e9098b5c2f3b7d118683e4418f4696
The
Joe Prostko wrote:
If I move the zlib.h inclusion below the crypto.h inclusion's #endif,
then Fossil compiles and works fine with both GCC2 and GCC4.
Fixed on trunk. Thanks for the report.
--
Joe Mistachkin
___
fossil-users mailing list
8 matches
Mail list logo