[prev in list] [next in list] [prev in thread] [next in thread]
List: fossil-users
Subject: Re: [fossil-users] libfossil + fuse
From: Stephan Beal <sgbeal () googlemail ! com>
Date: 2014-04-24 20:13:32
Message-ID: CAKd4nAgRKPiJmnt0vKJQ-q4aVL5wrpFW9BADx+m1A9o3vkLiNw () mail ! gmail ! com
[Download RAW message or body]
On Thu, Apr 24, 2014 at 10:05 PM, Stephan Beal <sgbeal@googlemail.com>wrote:
> On Thu, Apr 24, 2014 at 9:47 PM, Andy Goth <andrew.m.goth@gmail.com>wrote:
>
>> I'd like something similar with Fossil, though completion of libfossil is
>> an obvious prerequisite. Putting libfossil and fuse together could be the
>> way to go.
>>
>
> Feel free to come help out - as a registered Fossil dev you've already got
> the licensing prerequisite :).
>
BTW: libfossil already has all the core features needed for what you're
proposing, or at least has the infrastructure to support them easily. What
it's completely missing, in a nutshell:
- update/merge
- stash: relies on merge
- annotate: waiting on the devs to stop tweaking fossil's annotate so that
i can port it
- anything network related, including sync in any form
- full tickets support: relies heavily on th1, and i want to avoid tying
any given script language to the core lib
and that's the order those are likely to be tackled. Though update is not a
prereq for sync, the core lib will not know anything about networking.
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
[Attachment #3 (text/html)]
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Apr 24, 2014 \
at 10:05 PM, Stephan Beal <span dir="ltr"><<a href="mailto:sgbeal@googlemail.com" \
target="_blank">sgbeal@googlemail.com</a>></span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr"><div class="gmail_extra"><div class="gmail_quote"> <div class="">On Thu, \
Apr 24, 2014 at 9:47 PM, Andy Goth <span dir="ltr"><<a \
href="mailto:andrew.m.goth@gmail.com" \
target="_blank">andrew.m.goth@gmail.com</a>></span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I'd \
like something similar with Fossil, though completion of libfossil is an obvious \
prerequisite. Putting libfossil and fuse together could be the way to go.<br>
</blockquote><div><br></div></div><div>Feel free to come help out - as a registered \
Fossil dev you've already got the licensing prerequisite \
:).</div></div></div></div></blockquote><div><br></div><div>BTW: libfossil already \
has all the core features needed for what you're proposing, or at least has the \
infrastructure to support them easily. What it's completely missing, in a \
nutshell:</div> <div><br></div><div>- update/merge</div><div>- stash: relies on \
merge</div><div>- annotate: waiting on the devs to stop tweaking fossil's \
annotate so that i can port it<br></div><div>- anything network related, including \
sync in any form</div> <div>- full tickets support: relies heavily on th1, and i want \
to avoid tying any given script language to the core lib</div><div><br></div><div>and \
that's the order those are likely to be tackled. Though update is not a prereq \
for sync, the core lib will not know anything about networking.</div> \
<div><br></div></div>-- <br><div dir="ltr">----- stephan beal<br><a \
href="http://wanderinghorse.net/home/stephan/" \
target="_blank">http://wanderinghorse.net/home/stephan/</a><div><a \
href="http://gplus.to/sgbeal" target="_blank">http://gplus.to/sgbeal</a></div> \
<div>"Freedom is sloppy. But since tyranny's the only guaranteed byproduct \
of those who insist on a perfect world, freedom will have to do." -- Bigby \
Wolf</div></div> </div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic