On 12/17/2015 11:45 PM, Stephan Beal wrote:
On Thu, Dec 17, 2015 at 9:28 PM, Ross Berteig > wrote:
Build fossil with JSON support, then you get access to a bunch of
features with data transported in JSON with suitable quoting. I'm
i would be tickled pink to see you take that on :). i am more than happy to
help/support in any way, just can't currently commit (no pun intended) to
more than moderate amounts of typing, as my arm just can't do it. (That
doesn't rule out Skype or similar, though.)
- stephan
Sent from a
On 12/16/2015 6:42 PM, Ron W wrote:
Actually, I think it's "spread sheets". In the company I work for, it's
customers and it's suppliers, when we meet with "project managers" about
the status of issues, the PMs are presenting from their spread sheets
and updating them as we disuss the
On Thu, Dec 17, 2015 at 9:28 PM, Ross Berteig wrote:
>
> Build fossil with JSON support, then you get access to a bunch of features
> with data transported in JSON with suitable quoting. I'm not sure why JSON
> is not enabled in the official distributions, it works for me.
>
> > >> Would be nice if there was a "fossil ticket export" command that would
> > >> produce a "proper" CSV file. {snip}
> > > A problem with CSV is that there really isn't a clear definition of it
> at
> > > its edge cases other than testing what Excel will import correctly.
> >
> > Which is a
Scott Robison decía, en el mensaje "Re: [fossil-users] Rewrite of
fossil-v-git.wiki. Was: Fossil mentioned on HN" del 17/12/2015 21:12:09:
> Microsoft software has been exporting and importing CSV files for multiple
> decades. The CSV "standard" is just over one de
El 17/12/2015 a las 17:28, Ross Berteig escribió:
> On 12/16/2015 6:42 PM, Ron W wrote:
>> Would be nice if there was a "fossil ticket export" command that would
>> produce a "proper" CSV file. While "proper" is still something of a
>> debate, most spread sheet apps (Excel, LibreCalc,
might not be fault tolerant in the Enterprise marketing sense of the term,
but it's fairly tolerant of faults at various levels. ;) In any case, it's
undisputedly more tolerant of storage-system failures than git is.
- stephan beal, sgb...@googlemail.com
Written on a keyboard attached to a
On Wed, Dec 16, 2015 at 11:16 AM, Richard Hipp wrote:
> Based on comments on HN and on this mailing list, I have attempted to
> rewrite the fossil-v-git.wiki document
> (https://www.fossil-scm.org/fossil/doc/trunk/www/fossil-v-git.wiki) to
> better summarize the differences
Is a sql database fault tolerant? I guess so, but think that is not what
most people consider fault tolerant.
On Dec 16, 2015 9:36 AM, "Stephan Beal" wrote:
> Section 4.1: in fossil, but not git: fault-tolerant storage.
>
> - stephan beal, sgb...@googlemail.com
>
of fossil-v-git.wiki. Was: Fossil mentioned
on HN
Based on comments on HN and on this mailing list, I have attempted to
rewrite the fossil-v-git.wiki document
(https://www.fossil-scm.org/fossil/doc/trunk/www/fossil-v-git.wiki) to
better summarize the differences between the two products.
Your
Based on comments on HN and on this mailing list, I have attempted to
rewrite the fossil-v-git.wiki document
(https://www.fossil-scm.org/fossil/doc/trunk/www/fossil-v-git.wiki) to
better summarize the differences between the two products.
Your feedback on the rewrite, and especially suggestions
Section 4.1: in fossil, but not git: fault-tolerant storage.
- stephan beal, sgb...@googlemail.com
Written on a keyboard attached to a telephone attached to a TV screen, via
an app written for use on touchscreens. Please excuse brevity, typos, and
whatnot.
On Dec 16, 2015 5:16 PM, "Richard
13 matches
Mail list logo