On Jul 6, 2018, at 1:02 PM, Warren Young [email protected] wrote:
> Here’s my best-effort attempt at recreating what the OP described:
>
>https://imgur.com/a/6S4Y1nw
>
> You either end up with two trunk branches or a single branch plus a checkin
> off
> the trunk branch that also happens t
The other images/Dockerfiles which were available seemed to be stuck at older
versions of fossil. It is relatively simple to tweak the Dockerfiles to work
with newer versions of fossil, but I wanted something different. Whenever
someone reports an issue on the list, one of the first recommendati
got started - but I've learned some, so it wasn't all
wasted
time. I'll look at using fossil to provide the replication for itself and move
on
to the next service.
Thanks again for your insight.
- On Dec 21, 2017, at 4:10 PM, Warren Young [email protected] wrote:
> On D
e only service
in that category - I just started with fossil because I *thought* it would be an
easy win.
Thanks for your insight.
- On Dec 21, 2017, at 2:02 PM, Warren Young [email protected] wrote:
> On Dec 21, 2017, at 11:40 AM, [email protected] wrote:
>>
>> ranch2@
Dec 21 14:12 pkgReport.fossil
-rw-r--r-- 1 foouser foouser 596K Dec 21 11:31 servercfg.fossil
```
- On Dec 21, 2017, at 1:40 PM, dewey hylton [email protected] wrote:
> Unfortunately, my first stab at this failed:
>
> (gdb) break repo_list_page
> Breakpoint 1 at 0x7ccc0: f
Unfortunately, my first stab at this failed:
(gdb) break repo_list_page
Breakpoint 1 at 0x7ccc0: file ./src/main.c, line 1238.
(gdb) run http --repolist /fossils On 12/20/17, [email protected] wrote:
>> Would someone help me understand what I'm seeing here? I expec
Would someone help me understand what I'm seeing here? I expect a list of
repositories
in the web page output, but am told there are none. I've banged on this long
enough
to go cross-eyed, so I hope I'm just missing something very simple. I haven't
found
anything in the code that would cause thi
i have noticed the same thing (i believe the same ip address even) and have
it on my to-look-at list for later. so i'm glad you brought this up. :)
- On Sep 15, 2017, at 3:16 PM, John Found [email protected] wrote:
> I am not sure the problem is in fossil itself, but don't know from where
, andrew m goth [email protected] wrote:
> On 08/27/17 21:14, [email protected] wrote:
>> my static site generator leverages blackfriday for markdown parsing,
>> and pygment-colored code blocks are framed with "```" ... these blocks
>> do not get ignore
i've been playing with this quite a bit with some of my markdown sources,
including
those for one of my blogs. while it does exactly what i hoped it would do for
everything
i have tested in my fossil wikis, i did find one instance where it screws me up
on my
markdown-based blog. my static sit
> - On Aug 16, 2017, at 11:37 AM, Andy Goth [email protected] wrote:
>
> First off, I'm sorry I've been so incredibly busy with work and business
> travel, no time for Fossil development or even reading the mailing list.
> The only issues I've been able to dink on lately are those that w
this of course exists in its own fossil project, and is hosted in a public
location - but not one
which i'm willing to provide forever for an unknown number of folks. i don't
think this script
is that big of a deal, but one never knows ...
- On Aug 6, 2017, at 4:59 PM, dewey hylton wrote
in case it helps others, the entirety of my fossil project setup script can be
found here:
https://gist.github.com/dehylton/f8daa17bec33b5a1e58972675986c22f
this is the result of one of those "fun projects" which turned out to be useful
to me.
- On Aug 6, 2017, at 3:46 PM, dewey hylton
this is what i use in my setup script:
${FOSSIL} sqlite "insert or replace into config values ('project-name',
'${NAME}', now() );" -R "${FILE}" >/dev/null
- On Aug 6, 2017, at 4:06 AM, abhijit nandy wrote:
> I need to create quite a few repositories with many users so I've created a
>
what version of fossil are you using?
this seems to work fine for me, even when only specifying a destination
directory without the filename:
[0] [dewey@macchiato:~] $ fossil version
This is fossil version 1.34 [62dcb00e68] 2015-11-02 17:35:44 UTC
[0] [dewey@macchiato:~] $ mkdir -p foo
- On Jan 29, 2016, at 1:09 PM, Warren Young [email protected] wrote:
> On Jan 29, 2016, at 8:02 AM, [email protected] wrote:
>>
>> i'd like to
>> present the front page to everybody for an otherwise private repository.
>
> I seem to recall that in order
- On Jan 29, 2016, at 3:56 AM, Richard Hipp [email protected] wrote:
> On 1/28/16, [email protected] wrote:
>>
>> to be more specific, just in case ... my repo contains the following file:
>> docs/public/README.md
>>
>> i would like this to be the pa
- On Jan 27, 2016, at 11:44 PM, Dewey [email protected] wrote:
> - On Dec 10, 2015, at 12:47 PM, Paul Higham [email protected] wrote:
>
>> Thanx! This worked perfectly and, of course, the information was ‘hiding’ in
>> plain sight!
>>
>> :: paul
&g
i'm a command-line junkie, and tend to script/automate everything ... and i
tend to create a lot of fossil repos for small projects. so i'm trying to
figure out how to programmatically configure individual repos so that i don't
have to deal with the web browser for configuration.
i'm currently
19 matches
Mail list logo
