On Wed, 29 Feb 2012 18:32:19 -0800
Brian Smith br...@linuxfood.net wrote:
Hello Brian,
Here are some of the basic items that need feedback:
I've marked each question with an asterisk (*) so that you can find
my questions easier.
Let me say that, in general, I'd happy having same workflow as
On Fri, Mar 2, 2012 at 12:04 AM, Brian Smith br...@linuxfood.net wrote:
On Thursday, March 1, 2012 at 3:18 AM, Leo Razoumov wrote:
As a next step, I hope, one can augment limsync with a json API so
that power users can do more complex things.
I'm not sure what this would imply. The JSON
On Fri, Mar 2, 2012 at 03:50, Stephan Beal sgb...@googlemail.com wrote:
FYI: the JSON API doesn't aim to handle functionality which works directly
with a checkout, e.g. checkout, commit, pull, push, update. It's main aim is
to provide more or less the same data needed for implementing
On Fri, Mar 2, 2012 at 12:25 PM, Leo Razoumov slonik...@gmail.com wrote:
Correct me if I am wrong, but I think that JSON API can be used to
construct a list of artifacts in some non-trivial way.
It can be used to output/collect almost anything the fossil internals can
provide it (notable
Hi, I've been trying to implement a webservice that hosts fossil
repositories. Kinda like chiselapp.com . I have achieved running my own
server app written in golang to make the CGI requests in a routed handler
(i.e /user/repository ), but the problem I'm facing is that the only way I
can make it
On Fri, Mar 2, 2012 at 03:50, Stephan Beal sgb...@googlemail.com wrote:
Correct - i don't think we'll be able to do that kind of feature in JSON,
largely because JSON doesn't do binary. The closest thing to commit i
think we'll be able to portably/sensibly pull off is handling embedded docs
6 matches
Mail list logo
