On Tue, Jul 23, 2013 at 12:55 PM, Stephan Beal wrote:
> That's one of the beauties of restructuring fossil as a library: we don't
> need to embed any language at all. Instead, they can be built on top of the
> library.
>
Sure thing: but if that happens (which I'm rooting for), arguing about what
Hi,
Not aimed at anyone in particular, but if you are going to suggest a
particular language, can you please point to an interpreter that is easily
embeddable into fossil? That seems to be the problem with at least JS and
Python, and seems to be Lua's strong point. There's no point in discussing
+1 for a more common markup language (e.g. markdown) :)
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Hi,
Just my 2c: a JSON hook API a la Github would be fantastic.
Documentation: https://help.github.com/articles/post-receive-hooks
It would also hopefully make it easy to re-use existing services with
fossil, if the spec were sufficiently close :)
cheers
lvh
On Mon, Jul 22, 2013 at 12:10 PM,
Hi,
While, ceteris paribus, I'd certainly prefer Python, I definitely
understand that embedding CPython may be more trouble than it's worth. If
you are going to embed *something*, I'd vote for a langauge explicitly
designed with that purpose in mind, say, Lua.
However, if this is to happen, I rea
I attempted to, but perhaps I messed it up in some way. Message repeated
below.
---
Hi,
I've written a pretty small patch to make fossil serve files with extension
"mp4" as "video/mp4". This in accordance with RFC 4337[1].
The RFC says:
1. if neither audio nor video, use application/mp4
2. for
Would it be possible to include my rather small patch in the release? My
contributor agreement has been sent in, and the patch is about as small as
they come.
On Tue, Jun 18, 2013 at 7:49 PM, Stephan Beal wrote:
> On Tue, Jun 18, 2013 at 4:27 PM, Richard Hipp wrote:
>
>> Thanks for the updates
Hi,
I've written a pretty small patch to make fossil serve files with extension
"mp4" as "video/mp4". This in accordance with RFC 4337[1].
The RFC says:
1. if neither audio nor video, use application/mp4
2. for every other file, use video/mp4.
3. if only audio, you *may* use audio/mp4, but video
On Tue, May 28, 2013 at 5:25 PM, Richard Hipp wrote:
> On Tue, May 28, 2013 at 11:05 AM, Laurens Van Houtven <_...@lvh.io> wrote:
>
>>
>> My question about how this process with the "pending-review" branch works
>> was more about the mechanics of how you&#
On Tue, May 28, 2013 at 1:15 PM, Richard Hipp wrote:
> Fossil follows a BSD-style of code development, rather than a GPL-style.
>
I think my question may have been a bit ambiguous. I've pondered the
differences between those licenses a lot, and I very strongly prefer
permissive licenses.
(I've
On Tue, May 28, 2013 at 3:08 PM, Richard Hipp wrote:
> Survey: How many people know that in the web-based timeline for Fossil,
> you can click on any two nodes in the graph and get a diff between those
> two nodes?
>
I did not know that.
> And assuming I'm guessing correctly, do you have any
On May 28, 2013 12:39 PM, "Richard Hipp" wrote:
> There is a "pending review" branch (
http://www.fossil-scm.org/fossil/timeline?c=pending-review&y=ci) on the
Fossil self-hosting repository now!
I'm not sure I understand the workflow here. It seems the branch name
itself is "pending-review". Wher
Hi,
I'd like to know what sort of code review practices Fossil users employ. I
believe this has come up at least twice: I've asked about it myself back in
2010, and Russ Paielli from the Scala team in 2011.
All the projects I currently work on have some explicit form of code
review, be it:
- Gi
Hi,
I'd like to move some projects from Github to self-hosted fossil (or maybe
chisel, I haven't decided yet). However, I'd like to keep the Github
repository available and updated.
I can do a one-time move with fast-export/fast-import, but that doesn't
help for new code. I'm willing to have the
How difficult would it be to implement something like Launchpad's
merge proposals or Github's pull requests? We're currently using
Fossil the way drh described SQLite-like development processes and it
does indeed work very well, but it would be nice if there was a good
contributor story for the pro
For the people potentially checking out the Twisted script -- the
ticket with the bug just got fixed upstream, so there's basically a
one-release window where it was broken (10.2.0).
cheers
lvh
___
fossil-users mailing list
fossil-users@lists.fossil-scm
If I'm reading src/http.c correctly, that basically only happens if
iLength remains set to its original value of -1, so the response is
probably accurate. My best guess is that it's either a Bauk bug or
misconfiguration issue. Unfortunately I've never heard of Bauk, so I
can't really help you there
I do wonder why there aren't any newlines. Was that lost in the paste,
or is that really what Bauk produces as a response?
If my spec-memory is correct, HTTP defines a newline as a CR LF,
there's supposed to be one after each header, and the request ends
with a double newline. I can't see that in
That hostname isn't supposed to be internet-accessible, is it?
I've written an admittedly ad-hoc Twisted script which sort-of works
(depending on versions, you might get a duplicate Content-Type, which,
depending on browser (ie Chrome), may mean the CSS doesn't work). If
you want, you can try that
Yep, looks like it's a silly bug in some really old CGI serving code I
wasn't supposed to use but am going to fix now -- either way unrelated
to Fossil (which is, indeed, doing the right thing).
Sorry to bother you, happy new year :-)
lvh
___
fossil-use
Turns out I misinterpreted the Developer tool. Here's what's actually
in the HTTP header:
Content-Type: text/html
Content-Type: text/css; charset=utf-8
That doesn't look right. Still no idea where it's coming from though.
lvh
___
fossil-users mailing l
Hi :-)
First of all, happy new year (that was about half an hour ago) from
Belgium. May 2011 bring you good health and sane version control :-D
I've just tried to move my Fossil repo to a slightly more advanced
server (so I can do SSL and REMOTE_USER and friends), so I used
Twisted to write a CGI
Right, okay -- that's fairly reasonable, you couldn't realistically
prepare an attack on a repository then.
(The question of using things that are slower than SHA1 as in my
original post still stands, of course. As you've said, it's definitely
better than some stuff that gets used -- such as the r
Ahh, yes, I just realized you were probably talking about PBKDF1/2. My
apologies :-) That is a fair comparison, since they're both tunably
hard to compute KDFs.
cheers
lvh
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossi
On Thu, Dec 23, 2010 at 12:05 AM, Joerg Sonnenberger
wrote:
> On Thu, Dec 23, 2010 at 12:01:43AM +0100, Joerg Sonnenberger wrote:
>> Using scrypt wouldn't increase size much as most of the primitives exist
>> already. Using a format like $id$salt$encrypted like most UNIX systems
>> for passwd woul
On Thu, Dec 23, 2010 at 12:01 AM, Joerg Sonnenberger
wrote:
> On Wed, Dec 22, 2010 at 11:06:47PM +0100, Laurens Van Houtven wrote:
>> I was looking at
>> http://www.fossil-scm.org/index.html/doc/trunk/www/password.wiki and
>> worried about the case of a compromised reposi
On Wed, Dec 22, 2010 at 11:39 PM, Richard Hipp wrote:
> On Wed, Dec 22, 2010 at 5:06 PM, Laurens Van Houtven
> wrote:
>> Hi.
>>
>> I was looking at
>> http://www.fossil-scm.org/index.html/doc/trunk/www/password.wiki and
>> worried about the case of a com
Hi.
I was looking at
http://www.fossil-scm.org/index.html/doc/trunk/www/password.wiki and
worried about the case of a compromised repository. Why does Fossil
use SHA1 and not scrypt/bcrypt to store passwords?
thanks in advance (and happy holidays),
lvh
_
This would be totally awesome. Like the generic "just call a script"
event notification system, I think it's a great idea, because it makes
Fossil significantly more flexible without making it bloat up.
thanks,
lvh
___
fossil-users mailing list
fossil-us
Can you try it anyway in Firefox? I had a very similar redirect loop problem
with Chrome nightlies in a different app that magically went away with FF.
lvh
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/c
Richard,
Thank you very much for your reply. I'm interested in REMOTE_USER: what
Fossil docs should I be reading? How does this work with cloned
repositories? (I assume these users do exist when I clone a repository?)
thanks
lvh
___
fossil-users maili
Hi.
Let's say I have a development shop with a few developers and a similar
workflow (ticket states etc). Is there a recommended way of keeping this
configuration (including users if at all possible) in sync between multiple
Fossil repos? Can I just copy over the relevant tables and expect everyt
Hi!
I've found some mailing list mentions of Fossil + Buildbot, but never any
concrete success. Is anyone doing this? Specifically, does anyone
successfully push changes from Fossil to buildbot? I saw a patch for fossil
and some buildbot-specific code (involving their generic VCS integration
comm
Whoops, I accidentally sent this to the wrong list. Never mind me.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
No, I hadn't! That was very helpful, thank you.
I'm specifically interested in using conch as a server: using manhole
together with file transfer.
I've found some stuff from Tahoe-LAFS that uses it, but it's not
incredibly illuminating.
thanks for the pointer
lvh
Hi Richard,
First of all thanks for your reply.
Why we create branches: the idea in our workflow is that stuff in
trunk gets put to production (after a continuous integration system
runs all the tests on it). One of the steps between development and
production is mandatory code review. Obviously
2010/10/4 Lluís Batlle i Rossell :
> On Mon, Oct 04, 2010 at 10:55:02PM +0200, Laurens Van Houtven wrote:
> You can review against the trunk version it was updated from. As any DVCS,
> fossil does not provide methods to guarantee that noone commited over the same
> parent as you
Hello,
I'm trying to migrate a Trac workflow to Fossil. Here's what it looks like:
For each feature:
1. create ticket
2. create branch
3. implement
4. submit branch for review
5. review: if not good, back to 3
6. merge branch to trunk
(trunk gets handed off to continuous integration/deployment s
38 matches
Mail list logo
