The problem on Win7 seems to be that if the Windows build of fossil.exe
tries to use a Cygwin build of ssh.exe, it cannot invoke the ssh.exe
executable (fossil.exe says "cannot create child process"). A Cygwin build
of fossil.exe seems to work fine with Cygwin's ssh.exe.
Is this a known problem?
Thus said Joe Knapka on Thu, 09 Apr 2015 14:31:36 -0600:
> fossil clone ssh://me@server/repo.fossil?fossil=/home/me/bin/fossil
> local-repo.fossil --ssh-command=C:\cygwin\bin\ssh.exe
Maybe try:
fossil clone --ssh-command=C:\cygwin\bin\ssh.exe
ssh://me@server/repo.fossil?fossil=/home/me/bin/fo
Hello all,
Thank you, Andy and Ron, I can now clone and sync from my Linux client. My
colleague who is attempting this from his Win7 machine is not having so
much luck. (Actually it's me with a Win7 machine, but I'm trying to figure
it out so I can concisely tell my colleague how to do it on his W
On 4/9/2015 12:00 PM, David Mason wrote:
> I use symlinks a lot. I *really* wish fossil handled them "properly".
>
> This is one of my biggest beefs about fossil.
Fossil's driving requirement is to support the development of SQLite,
and its applicability anywhere else is just a bonus. Since SQL
Thanks for the examples, Andy.
I use symlinks a lot. I *really* wish fossil handled them "properly".
This is one of my biggest beefs about fossil.
The other big one is that if I set some property (in this case
allow-symlinks true) and I also set the corresponding .fossil-setting I get
a warning
Thus said Ron W on Thu, 09 Apr 2015 11:55:14 -0400:
> Also note that the SSH command to be used can be specified by the
> --ssh-command= option. (But the fossil= URL parameter is easier in
> this situation.)
The two options are not really related.
The --ssh-command option does not defi
On 4/8/2015 2:44 PM, David Mason wrote:
> Here is another problem with symlinks:
>
> [add files in a subdirectory]
> [commit]
> [move subdirectory outside of repository]
> [create symlink to subdirectory with same name as original]
> [Fossil doesn't notice anything happened]
> Same problem if you
On Thu, Apr 9, 2015 at 12:07 AM, Matt Welland
wrote:
>
> On Wed, Apr 8, 2015 at 5:57 PM, Andy Bradford
> wrote:
>
>> Thus said Matt Welland on Wed, 08 Apr 2015 08:27:00 -0700:
>>
>> > What we are seeing is that forks happen due to simultaneous, partially
>> > overlapping, commits and that neit
On Thu, Apr 9, 2015 at 11:21 AM, Andy Bradford
wrote:
>
> If Fossil is not installed in the normal system PATH, you can instruct
> the client to clone using the fossil query parameter. For example, if
> you have installed fossil in ~/bin/fossil you can clone like:
>
> fossil clone ssh://user@
On Thu, Apr 9, 2015 at 7:43 AM, Andy Bradford
wrote:
> Thus said Matt Welland on Wed, 08 Apr 2015 21:07:00 -0700:
>
> > Would it be possible to detect and warn on update, status and push?
>
> What about pull??
>
> E.g. if I pull in new content that creates a fork should the pull issue
> a warnin
Thus said Joe Knapka on Thu, 09 Apr 2015 08:51:05 -0600:
> I am attempting to sync with a Fossil repo that is on a machine to
> which I have no administrative access, via ssh. I have installed
> fossil in ~/bin, added ~/bin to the PATH in .bash_profile, and ensured
> that I can run fossi
Hello all,
I am attempting to sync with a Fossil repo that is on a machine to which I
have no administrative access, via ssh. I have installed fossil in ~/bin,
added ~/bin to the PATH in .bash_profile, and ensured that I can run fossil
normally from the command line when I log in.
When I attempt
This is the timeline from that repo. If there is data to sync and you are
in the 0b2ff node then you get the double WARNING.
[image: Inline image 1]
On Wed, Apr 8, 2015 at 11:01 PM, Andy Bradford
wrote:
> Thus said Matt Welland on Wed, 08 Apr 2015 22:39:36 -0700:
>
> > > > Server says: ** WA
Thus said Matt Welland on Wed, 08 Apr 2015 21:07:00 -0700:
> Would it be possible to detect and warn on update, status and push?
What about pull??
E.g. if I pull in new content that creates a fork should the pull issue
a warning?
Thanks,
Andy
--
TAI64 timestamp: 40005526904a
__
So, got some time for this again.
The good news, the patch will work like expected and even support the
definition of the listening address. Some working examples (changed IPv6
address for reason):
beowulf@:~/fossil$ ./fossil server -P
34cd::ab12:1234:a12b:12ab:1ab2:34cd:3cd4:8889 ../fossil.fossi
15 matches
Mail list logo
