On Fri, Jan 11, 2013 at 3:34 AM, Miles Fidelman
wrote:
> 1. As the documentation indicates, there's no support for working with
> branching and merging of stand-alone wiki pages, which suggests that .wiki
> pages within a code tree are more manageable. But. they don't seem to
> be editable th
I'm implementing a "Changed Tickets" report similar to that in Fossil's ticket
system, the main difference is I want to show who made the change. I do this by
joining ticket and ticketchg
SELECT DISTINCT
date(ticket.tkt_mtime),
substr(tkt_uuid,1,10) AS '#',
status,
login,
t
On Jan 11, 2013, at 00:47 , wrote:
> My use case here is that I've got repositories hosted on
> http://fossil.io7m.com but I've also got an exact mirror of that site
> on my internal network here that's used for testing quickly on multiple
> machines/VMs (and will now be polled very frequently f
On Wed, 09 Jan 2013 12:10:35 +0100, Gilles
wrote:
>Am I correct in understanding that this is the right way to proceed to
>try some new code, and either save it (whether it works or not, just
>as a track-record) or discard it?
So the right way to experiment and keep tried code for later reference
Stephan Beal wrote:
On Fri, Jan 11, 2013 at 3:34 AM, Miles Fidelman
mailto:mfidel...@meetinghouse.net>> wrote:
1. As the documentation indicates, there's no support for working
with branching and merging of stand-alone wiki pages, which
suggests that .wiki pages within a code tree a
On Thu, Jan 10, 2013 at 9:34 PM, Miles Fidelman
wrote:
>
> 1. As the documentation indicates, there's no support for working with
> branching and merging of stand-alone wiki pages, which suggests that .wiki
> pages within a code tree are more manageable. But. they don't seem to
> be editable
On Fri, 11 Jan 2013 13:06:17 +0100
Gilles wrote:
>> Am I correct in understanding that this is the right way to proceed
>> to try some new code, and either save it (whether it works or not,
>> just as a track-record) or discard it?
>
> So the right way to experiment and keep tried code for later
On Fri, Jan 11, 2013 at 2:12 PM, Miles Fidelman
wrote:
> Actually my question was, are embedded documentation pages editable
> through the web gui?
No, unfortunately not. This feature idea has been floated around a few
times, but the commit mechanism really needs a checkout to work with, and
se
On Fri, Jan 11, 2013 at 3:07 AM, Steve Landers wrote:
> I'm implementing a "Changed Tickets" report similar to that in Fossil's
> ticket system, the main difference is I want to show who made the change. I
> do this by joining ticket and ticketchg
>
> SELECT DISTINCT
> date(ticket.tkt_mtime),
On Fri, Jan 11, 2013 at 8:37 AM, Richard Hipp wrote:
>
> The "status" field is coming from the ticket table and thus shows the
> latest status. To show the latest status at some point in the past, you
> need a (I think) to first add a "status" field to your "ticketchng" table
> definition. Then
On Fri, 11 Jan 2013 17:19:40 +0400, Konstantin Khomoutov
wrote:
>> and how to check the changes made in a branch to such and such file,
>
>Fire up Fossil web UI and click on the links marked "patch" and "diff"
>in the commit view.
This is really what I want to do: Being able to see all the things
On Fri, 11 Jan 2013 17:11:44 +0100, Gilles
wrote:
>This is really what I want to do: Being able to see all the things I
>tried on a file in the branch. Most of the time, I want to keep track
>of things I tried just in case instead of just forgetting about them
>with "fossil revert".
What I'm driv
On Fri, 11 Jan 2013 17:11:44 +0100
Gilles wrote:
> >Fire up Fossil web UI and click on the links marked "patch" and
> >"diff" in the commit view.
>
> This is really what I want to do: Being able to see all the things I
> tried on a file in the branch. Most of the time, I want to keep track
> of
On Fri, 11 Jan 2013 17:25:24 +0100
Gilles wrote:
[...]
> What I'm driving at:
> 1. Keep tried but NOK algos in a branch called eg. "experimental"
> 2. Find a simple way to locate old algo's I know I tried before by
> searching Fossil, regardless of which branch they are (trunk or
> experimental).
On Fri, 11 Jan 2013 11:36:10 +0100
Remigiusz Modrzejewski wrote:
>
> On Jan 11, 2013, at 00:47 ,
> wrote:
>
> > My use case here is that I've got repositories hosted on
> > http://fossil.io7m.com but I've also got an exact mirror of that
> > site on my internal network here that's used for testi
my question regards the (very useful!) functionality of selecting
(clicking) two timeline entries in the web GUI to the repo for diffing.
this works alright for me with a certain (remote) repository.
it does +not+ work for the local copy of that repo or any other local repo
(under URL http://
On Fri, Jan 11, 2013 at 12:45 PM, j. van den hoff wrote:
> my question regards the (very useful!) functionality of selecting
> (clicking) two timeline entries in the web GUI to the repo for diffing.
> this works alright for me with a certain (remote) repository.
>
> it does +not+ work for the loc
On Fri, Jan 11, 2013 at 3:07 AM, Steve Landers wrote:
> I'm implementing a "Changed Tickets" report similar to that in Fossil's
> ticket system, the main difference is I want to show who made the change. I
> do this by joining ticket and ticketchg
>
How is the /timeline?y=t page is insufficient f
On Fri, 11 Jan 2013 18:57:34 +0100, Richard Hipp wrote:
On Fri, Jan 11, 2013 at 12:45 PM, j. van den hoff
wrote:
my question regards the (very useful!) functionality of selecting
(clicking) two timeline entries in the web GUI to the repo for diffing.
this works alright for me with a certai
On Thu, 10 Jan 2013 13:51:51 +0100, Stephan Beal
wrote:
On Thu, Jan 10, 2013 at 1:35 PM, Stephan Beal
wrote:
i'll sign up for adding that - i would be able to do this on Sunday. i
would add it to the "status" command because we have that info in the
/stat
page already (and in "fossil
On Fri, Jan 11, 2013 at 9:04 PM, j. v. d. hoff wrote:
> checkin-count: 4845
>
> however, I do see a total (files+wiki+ticket) of 8799 checkins and
>
> fossil time -t ci -n 1|grep ^[0-9]|wc -l
>
> yields 4009.
>
> so what is `checkin-count' actually reporting??
>
"Whatever is shown in the /sta
Stephan Beal wrote:
On Fri, Jan 11, 2013 at 2:12 PM, Miles Fidelman
mailto:mfidel...@meetinghouse.net>> wrote:
Actually my question was, are embedded documentation pages
editable through the web gui?
No, unfortunately not. This feature idea has been floated around a few
times, but t
On 11/01/2013, at 9:44 PM, Richard Hipp wrote:
> The "status" field is coming from the ticket table and thus shows the latest
> status. To show the latest status at some point in the past, you need a (I
> think) to first add a "status" field to your "ticketchng" table definition.
> Then modi
23 matches
Mail list logo
