two things:
1.
in autosync mode, one can do `fossil up' to pull/push changes and
integrate them into the checkout which mostly prevents unnecessary forking
etc. this is (for good reason) listed as one notable advantage of `fossil'
over other DVCSs.
however, (local) changes to the wiki
2013/10/28 Ron Wilson ronw.m...@gmail.com:
In any case, the cert displayed did not look like a self-signed cert, so I
would be
concerned that the incorrect cert was displayed.
The jan-httpsproxytunnel branch doesn't change anything
related to certificate handling. I just included the full logs
The fossil update command does a fossil pull in autosync mode. The
fossil commit command first does a fossil pull, then does the check-in,
then does a fossil push.
This has nothing to do with content. The sync mechanism in Fossil does not
distinguish between wiki or tickets or checked-in files.
On Tue, 29 Oct 2013 12:53:59 +0100, Richard Hipp d...@sqlite.org wrote:
The fossil update command does a fossil pull in autosync mode. The
fossil commit command first does a fossil pull, then does the
check-in,
then does a fossil push.
This has nothing to do with content. The sync
On Tue, Oct 29, 2013 at 5:47 AM, Jan Nijtmans jan.nijtm...@gmail.comwrote:
2013/10/28 Ron Wilson ronw.m...@gmail.com:
Beyond, I think there should be a choice between yes, just this time
and
always now and all future times, specifically, yes for the duration of
this
command, since
2013/10/29 Ron Wilson ronw.m...@gmail.com:
Thanks for your fix for proxying HTTPS session.
I assume that's directed to Jan Danielsson, not to me
(although my name is Jan too..)
Regards,
Jan Nijtmans
___
fossil-users mailing list
On Tue, Oct 29, 2013 at 8:43 AM, j. van den hoff
veedeeh...@googlemail.comwrote:
I principally have not thought otherwise. the problem is that wiki
changes are not commited but are done (and integrated into the repo) via
the ui.
A quick look through the Fossil documentation, I don't see any
On Tue, Oct 29, 2013 at 11:54 AM, Jan Nijtmans jan.nijtm...@gmail.comwrote:
2013/10/29 Ron Wilson ronw.m...@gmail.com:
Thanks for your fix for proxying HTTPS session.
I assume that's directed to Jan Danielsson, not to me
(although my name is Jan too..)
Oops. Yes, it is. My apologies
On Tue, 29 Oct 2013 17:00:58 +0100, Ron Wilson ronw.m...@gmail.com wrote:
On Tue, Oct 29, 2013 at 8:43 AM, j. van den hoff
veedeeh...@googlemail.comwrote:
I principally have not thought otherwise. the problem is that wiki
changes are not commited but are done (and integrated into the repo)
On 28/10/13 13:39, Jan Nijtmans wrote:
[---]
Conclusion: your branch works fine as long as the password is
not taken from the (https) url.
I hope this feedback is useful to you.
Yes, very useful. We only use client certificates, and apache is set
up to set REMOTE_USER from the client
10 matches
Mail list logo
