Re: [fossil-users] Excessively long path length breaks working copy on Windows 7

Thus said Stephan Beal on Mon, 01 Dec 2014 21:22:56 +0100: > This server could not prove that it is *fossil-scm.org > *; its security certificate is from *sqlite.org > *. This may be caused by a misconfiguration or an > attacker intercept

Re: [fossil-users] Corrupt line endings in cat/finfo on Windows with CR+LF files

On Mon, Dec 1, 2014 at 5:26 PM, bch wrote: > This sounds like "pull request" functionality, in a way -- is that the > concept ? > > Yeah. The branch name "DBP-workflow" stands for "Drive By Patch workflow". And a Drive-By-Patch and a Pull-Request are basically the same thing, right? These idea

Re: [fossil-users] Corrupt line endings in cat/finfo on Windows with CR+LF files

This sounds like "pull request" functionality, in a way -- is that the concept ? -bch On 12/1/14, Richard Hipp wrote: > On Mon, Dec 1, 2014 at 5:07 PM, Warren Young wrote: > >> I'm happy to let people check their changes into their own private clone. >> I just want a one-line command I can giv

Re: [fossil-users] Corrupt line endings in cat/finfo on Windows with CR+LF files

On Mon, Dec 1, 2014 at 5:07 PM, Warren Young wrote: > I’m happy to let people check their changes into their own private clone. > I just want a one-line command I can give to my anonymous cloners that they > can use to send me a copy of what they have wrought, when they think > they’ve done somet

Re: [fossil-users] Corrupt line endings in cat/finfo on Windows with CR+LF files

On Nov 27, 2014, at 1:43 AM, Ron W wrote: > If I allow anonymous cloning and pulling on my Fossil repo, you can > clone/pull from it, no different than a Github repo. Of course. I’m just saying that this is automatic with Github. Everyone who uses the service automatically gets a public-faci

Re: [fossil-users] Excessively long path length breaks working copy on Windows 7

On 2014-12-01T21:23:53 +0100 Stephan Beal wrote: > On Mon, Dec 1, 2014 at 9:22 PM, Stephan Beal wrote: > > > Strange: when i follow the link you posted, Chromium tells me (for the > > first time ever, possibly b/c i've never knowingly accessed it over https): > > > > This server could not prove

Re: [fossil-users] Excessively long path length breaks working copy on Windows 7

On Mon, Dec 1, 2014 at 9:22 PM, Stephan Beal wrote: > Strange: when i follow the link you posted, Chromium tells me (for the > first time ever, possibly b/c i've never knowingly accessed it over https): > > This server could not prove that it is *fossil-scm.org > *; its sec

Re: [fossil-users] Excessively long path length breaks working copy on Windows 7

On Mon, Dec 1, 2014 at 8:34 PM, wrote: > > https://fossil-scm.org/index.html/tktview/81b89131083cd01af0547e3cc0a17960512d04aa FYI: the ticket and attachment have been moderated through. Strange: when i follow the link you posted, Chromium tells me (for the first time ever, possibly b/c i've ne

Re: [fossil-users] Allowed pages for th1 `query`?

Bump? Could anyone clarify where TH1 'query' will be taken? Thanks, Tomek > Date: Wed, 26 Nov 2014 10:44:34 -0500 > From: Tomek Kott > To: "fossil-users@lists.fossil-scm.org" > > Subject: [fossil-users] Allowed pages for th1 `query`? > Message-ID: > Content-Type: text/plain; charset="is

Re: [fossil-users] Fossil wiki parsing code

On Mon, Dec 01, 2014 at 08:18:06PM +0100, Stephan Beal wrote: > On Mon, Dec 1, 2014 at 8:00 PM, Richard Hipp wrote: > > > Never been separated out, as far as I know. But you'll find all the code > > in the single file named wikiformat.c. It shouldn't be that hard to > > separate from the rest o

Re: [fossil-users] Fossil wiki parsing code

On Mon, Dec 01, 2014 at 08:22:49PM +0100, Stephan Beal wrote: > On Mon, Dec 1, 2014 at 8:11 PM, James Turner wrote: > > > Yup, was just browsing wikiformat.c. I'll share what I come up with. I > > also plan on creating a lua wrapper for it as my app is written in lua. > > > > fwiw (oh, come on,

Re: [fossil-users] Excessively long path length breaks working copy on Windows 7

On 2014-11-15T16:57:23 + wrote: > 'Lo. > > I seem to have run into a problem that I can reproduce with the > following repository: > > http://waste.io7m.com/2014/11/15/fossil-pathbug.fossil > I've filed a bug so that this doesn't get lost to time: https://fossil-scm.org/index.html/tktv

Re: [fossil-users] Fossil wiki parsing code

On Mon, Dec 1, 2014 at 8:11 PM, James Turner wrote: > Yup, was just browsing wikiformat.c. I'll share what I come up with. I > also plan on creating a lua wrapper for it as my app is written in lua. > fwiw (oh, come on, most of you knew this was coming ;)... Depending on the features you need,

Re: [fossil-users] Fossil wiki parsing code

On Mon, Dec 1, 2014 at 8:00 PM, Richard Hipp wrote: > Never been separated out, as far as I know. But you'll find all the code > in the single file named wikiformat.c. It shouldn't be that hard to > separate from the rest of the system. > Unless i'm mistaken, the block in question is: https:/

Re: [fossil-users] Fossil wiki parsing code

On Mon, Dec 01, 2014 at 02:00:45PM -0500, Richard Hipp wrote: > On Mon, Dec 1, 2014 at 1:30 PM, James Turner wrote: > > > I was curious if anyone has separated the fossil wiki parsing/formatting > > code from fossil into a standalone library? > > > > Never been separated out, as far as I know.

Re: [fossil-users] Fossil wiki parsing code

On Mon, Dec 1, 2014 at 1:30 PM, James Turner wrote: > I was curious if anyone has separated the fossil wiki parsing/formatting > code from fossil into a standalone library? > Never been separated out, as far as I know. But you'll find all the code in the single file named wikiformat.c. It shou

[fossil-users] Fossil wiki parsing code

I was curious if anyone has separated the fossil wiki parsing/formatting code from fossil into a standalone library? I was looking to use it in my own project as an alternative to markdown and figured I'd check before doing it myself. Thanks. -- James Turner _