Don't forget that fossil has the wiki+issues in the repo, so if
chiselapp.com (or your host) with your repo would go down, you wouldn't
lose those, as opposed to issue tracking being gone if github goes down. Of
course, this is disregarding network effects and discoverability, but for
those you
:password"
:end
On 26 November 2015 at 00:56, Warren Young <w...@etr-usa.com> wrote:
> On Nov 25, 2015, at 3:56 PM, Dömötör Gulyás <dognot...@gmail.com> wrote:
> >
> > Ah, great idea, I'll give that a try! We'll see just how rusty my
> windows batch file skills ar
Do any of you use Fuel? Parts of my team don't want to use the command line
(or can't, due to not having rights to the windows command line) and Fuel
seems like a decent GUI, except I can't figure out how to configure it to
use --httpauth.
It also seems to ignore the settings in the fossil repo,
Ah, great idea, I'll give that a try! We'll see just how rusty my windows
batch file skills are.
I’m not a Fuel user, but I just installed 1.0.1 on my Windows 10 test VM,
> and I see File > Preferences... > Fossil Path. That should allow you to
> write a wrapper script that calls fossil.exe with
We seem to be able to make fossil do things via windows shortcuts. And Fuel
runs fine, except that it's apparently impossible to configure it to use
--httpauth, or to make it use the url and credentials stored in the fossil
repo.
I have no control over the fact that work PCs are locked down in
will just read it, and when changes are
to be made, it'll be on me to manage merging anyway. This really isn't a
software company :/
On 18 November 2015 at 02:05, Ron W <ronw.m...@gmail.com> wrote:
> On Tue, Nov 17, 2015 at 6:06 PM, Dömötör Gulyás <dognot...@gmail.com>
> wrote:
t 5:57 PM, Dömötör Gulyás <dognot...@gmail.com>
> wrote:
>
>> I've got an environment where it'd be good to put a fossil repo onto a
>> windows network share, as running an actual server is hindered by corporate
>> IT policy. Has anybody done this, or is this at least th
I've got an environment where it'd be good to put a fossil repo onto a
windows network share, as running an actual server is hindered by corporate
IT policy. Has anybody done this, or is this at least theoretically doable?
Cheers & thanks,
DG
___
Wether you like tabs or spaces, both are widely enough used to
consider a setting for display purposes in the Web UI.
On 30 September 2014 23:01, Zoltán Kócsi zol...@bendor.com.au wrote:
On Tue, 30 Sep 2014 12:12:11 -0400
Ron W ronw.m...@gmail.com wrote:
On Tue, Sep 30, 2014 at 10:01 AM,
Yes, that's exactly my use case, exacerbated by the fact that
FileMerge/opendiff are real slow when used from fossil/git/bzr per
file, taking on the order of seconds for every file it has to show,
which doesn't happen when used from the GUI (radr #16400583 in
bugreport.apple.com). Additionally
When using fossil gdiff on OS X, with opendiff as the gdiff command,
diffs for all files are shown, even if there are no changes. This
contrasts with behavior of opendiff with git/bzr, etc, which only show
the changed files, which is preferrable.
Is there a known workaround for this? Out of the
:
On Wed, Sep 24, 2014 at 12:35 PM, Dömötör Gulyás dognot...@gmail.com
wrote:
When using fossil gdiff on OS X, with opendiff as the gdiff command,
diffs for all files are shown, even if there are no changes. This
contrasts with behavior of opendiff with git/bzr, etc, which only show
Aha, so for me also on 1.29, if i specify src/*, it shows all files,
but just gdiff with no paths shows the changes only.
Now, the problem is I can't tell fossil to fossil gdiff src/, it
insists on fossil gdiff src/*, so it explicitly loads up all the
files. Any suggestions? My workflow is such
, Dömötör Gulyás dognot...@gmail.com
wrote:
I wish to migrate several bzr repos to fossil 1.29, and have gotten
stuck at fossil telling me cannot handle R records, use --full-tree
trying to import the fast-import dumps. Is there a workaround for this
issue? I have seen only one reference
I wish to migrate several bzr repos to fossil 1.29, and have gotten
stuck at fossil telling me cannot handle R records, use --full-tree
trying to import the fast-import dumps. Is there a workaround for this
issue? I have seen only one reference to this issue on this ML, from
last May, but no
On 2 September 2014 10:08, John Long codeb...@inbox.lv wrote:
7) A source control system should be sensible from the point of view of the
person using it to manage source code. It should not be Linux-centric. It
should not require you to understand its internals to use it effectively
An interesting scenario, what is there to be learned from it for
fossil? Since fossil doesn't like history rewrites, are we protected
to some degree from falsified commits? (I ask as I have not yed had
the opportunity to look into fossil's security features extensively)
On 1 June 2014 06:43, B
17 matches
Mail list logo
