they could display the usual
ticket or check-in overview.
Closing
---
Hope that helps,
Chris Peachment
On Mon, 2013-02-18 at 13:48 +0100, Natacha Porté wrote:
> Hello,
>
> a while back it has been brought to my attention that markdown-in-fossil
> behaves differently than fossil
I've just this moment faced this problem. The Linux executable
available from www.fossil-scm.org does not run on Bluehost and
reports an error unable to find libz.so.1
As John Found says, it is a problem related to the 64 bit
environment and missing 32 bit libraries.
My solution was to work at th
On Sat, 2012-08-11 at 12:32 -0400, Richard Hipp wrote:
> Enhancements to Fossil to support WYSIWYG editing of wiki pages are
> now in the wysiwyg branch of the Fossil self-hosting repository.
>
> A sandbox repository with open permissions and with WYSIWYG editing
> turned on has been created at ht
On Sat, 2012-06-23 at 14:14 +0200, Stephan Beal wrote:
> On Sat, Jun 23, 2012 at 1:23 PM, Miles Fidelman
> wrote:
> Stephan Beal wrote:
> Fossiloid was actually my very first choice, but has
> the drawback that the "oid" suffix normally refers to
>
It looks to me like you could add a new field to the 'ticket' table,
say PatientIdentifier of type text, and enter its value as part of
the ticket add function. A new report selecting on this new field
would provide the view of all tickets ordered by PatientIdentifier.
The missing part is some way
On Thu, 2012-02-23 at 08:54 -0500, Richard Hipp wrote:
>
> I can't tell from the text that follows if you are setting up the
> login-groups right or not. The correct way to do it is as follows:
>
> A. Login via browser to b.fossil. Go to the /Admin/Login-Groups
> screen and join a.fossil.
> B.
On Wed, 2012-02-01 at 09:03 -0500, Leo Razoumov wrote:
> On Wed, Feb 1, 2012 at 07:08, Richard Hipp wrote:
> > The clock according to the "D" card of the artifact.
> >
> > In other words, you can keep changing the value of a tag and the latest
> > version always wins.
> >
> > If two people change
I REALLY like the appearance of the markdown output. I had not
appreciated the limitations of standard fossil wiki markup since
I generally pay more attention to content than to appearance.
And the raw text is quite readable in its original form.
Taking a suggestion posed in the original document,
+1
On Fri, 2011-12-02 at 16:19 +0100, Lluís Batlle i Rossell wrote:
> Hello,
>
> event changes don't appear in the timeline. Maybe they should appear, as
> ticket
> or commit changes appear?
>
> Regards,
> Lluís.
> ___
> fossil-users mailing list
> fo
I revealed my own ignorance with this comment:
3. Only the checkin ('ci') and commit ('co') commands have been
abbreviated. Others use the full word for the command. Perhaps
a small note at the end about the ability to abbreviate would
be a reminder to those with greater experience.
I should have
Thank you for providing a great assistance to novice users.
I and the eight person team with which I work are such and
this will be a useful addition.
Some notes:
1. Not all readers will be programmers and not all will have
English as first language. The combination makes for extra
work to unders
ote:
>
> >
> > On Sun, Nov 20, 2011 at 7:56 PM, Chris Peachment wrote:
> >> I'm using fossil version 1.20 on Linux for both server and client
> >> computers.
> >>
> >> I want to use fossil command line instructions to initialise an
> >> empty r
ne of
many repositories.
On Sun, 2011-11-20 at 20:13 -0500, Richard Hipp wrote:
>
>
> On Sun, Nov 20, 2011 at 7:56 PM, Chris Peachment
> wrote:
> I'm using fossil version 1.20 on Linux for both server and
> client
> computers.
>
>
t clear if the above action
was the cause of the behaviour seen prior that ticket.
As secondary issues, I can not find commands to supply the
project-name and user info fields.
And it would be nice to insert a wiki page (specifically the
home page) from the command line too.
Thanks f
I'm a novice Fossil user working in a small group with need
to track both text and binary files.
It seems to me that locks are nice to have for text files
since 3 way diffs can be merged at relatively little cost.
But inability to merge binary files might mean painful hand
merging based on side by
This appears to fix the inability to change 'assigned_to'
and other fields in the same edit.
But creating a new ticket and specifying something other
than 'unassigned' for this field does not appear to save
the assignment as part of the ticket create function.
In addition, the selection list valu
16 matches
Mail list logo
