[fossil-users] bitkeeper open sourced, and DSCM discussion and history

Interesting discussion going on at Hacker News currently. https://news.ycombinator.com/item?id=11667494 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] bitkeeper open sourced, and DSCM discussion and history

On May 11, 2016, at 9:27 AM, bch wrote: > > Interesting discussion going on at Hacker News currently. > > https://news.ycombinator.com/item?id=11667494 Thanks. I think I adequately-addressed the one anti-Fossil comment there. Slashdot’s take on this article was kind of

Re: [fossil-users] Unrecognized command-line option, or missing argument: --https

On May 11, 2016, at 1:58 PM, Piotr Orzechowski wrote: > > "At this stage, the standalone server (e.g. "fossil server") does not support > SSL.” The standard advice is to tell the fossil server to bind to localhost (as you’re already doing) and put it behind stunnel

Re: [fossil-users] How to create a ticket link in the wiki?

On May 11, 2016, at 3:52 PM, Marko Käning wrote: > > Referring to tickets on a wiki page like this: [968eb6376d] doesn't work, > where one would have to use [968eb6376d](tktview?name=968eb6376d). > > Is this intended, or am I missing something? Yes, it’s a known

Re: [fossil-users] How to create a ticket link in the wiki?

On 5/11/16, Marko Käning wrote: > Referring to tickets on a wiki page like this: [968eb6376d] doesn't work, > where one would have to use [968eb6376d](tktview?name=968eb6376d). > This is only a problem with Markdown, because Markdown uses the Markdown spec for

[fossil-users] How to create a ticket link in the wiki?

Referring to tickets on a wiki page like this: [968eb6376d] doesn't work, where one would have to use [968eb6376d](tktview?name=968eb6376d). Is this intended, or am I missing something? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org

[fossil-users] Feature request: auto-closing of tickets a la Trac

An auto-closing of tickets if the commit comment contains stg like "closed [TICKETID]", "closes [TICKETID]", "fixed [TICKETID]", "fixes [TICKETID]", would be nice. This is possible to set up in Trac for instance... ___ fossil-users mailing list

Re: [fossil-users] Timestamps in ticket overview pages not shown in local time

On May 11, 2016, at 3:51 PM, Marko Käning wrote: > > Timestamps in ticket overview pages I think I see what you mean. Both the mtime column in /rptview URLs and the User Comments boxes in ticket /info pages use UTC. But, if you uncheck Admin > Timeline > Use

Re: [fossil-users] How to create a ticket link in the wiki?

On May 11, 2016, at 4:38 PM, Richard Hipp wrote: > > On 5/11/16, Marko Käning wrote: >> Referring to tickets on a wiki page like this: [968eb6376d] doesn't work, >> where one would have to use [968eb6376d](tktview?name=968eb6376d). >> > > This is

[fossil-users] Suggestions for list of branches in web-UI

Hi devs, while using Fossil’s web-UI I noticed some things regarding the display of branches. 1) It would be nice, if private branches were marked in /brlist somehow, preferably by introducing a new column entitled “Private”, or stg similar. 2) /brlist should NOT show closed branches (but

[fossil-users] Feature request: Markdown formatting in ticket comments

It would be nice if ticket comments would use Markdown formatting as well. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] fossil timeline on console quirk with ticket titles

Why does "fossil timeline" show HTML tags around ticket titles, like this: Ticket test ??? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Timestamps in ticket overview pages not shown in local time

On 12 May 2016, at 00:26 , Warren Young wrote: > On May 11, 2016, at 3:51 PM, Marko Käning wrote: >> >> Timestamps in ticket overview pages > > I think I see what you mean. Both the mtime column in /rptview URLs and the > User Comments boxes in

Re: [fossil-users] How to create a ticket link in the wiki?

On 12 May 2016, at 00:38 , Warren Young wrote: > On May 11, 2016, at 3:52 PM, Marko Käning wrote: >> >> Referring to tickets on a wiki page like this: [968eb6376d] doesn't work, >> where one would have to use [968eb6376d](tktview?name=968eb6376d).

[fossil-users] Timestamps in ticket overview pages not shown in local time

Timestamps in ticket overview pages aren't local time (as in the ticket view page), but UTC, which is irritating. Can this be configured differently someplace? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org

Re: [fossil-users] Feature request: Markdown formatting in ticket comments

On May 11, 2016, at 3:56 PM, Marko Käning wrote: > > It would be nice if ticket comments would use Markdown formatting as well. It’s been requested many times. All that’s wanted is for someone to get around to writing the code and submitting it, I suspect.

Re: [fossil-users] Feature request: auto-closing of tickets a la Trac

On May 11, 2016, at 3:57 PM, Marko Käning wrote: > > An auto-closing of tickets if the commit comment contains stg like "closed > [TICKETID]", "closes [TICKETID]", "fixed [TICKETID]", "fixes [TICKETID]", > would be nice. Agreed. The only problem is the perennial

Re: [fossil-users] Timestamps in ticket overview pages not shown in local time

On May 11, 2016, at 4:39 PM, Marko Käning wrote: > > On 12 May 2016, at 00:26 , Warren Young wrote: > >> I volunteer you. :) > > Oh. I never had a look inside Fossil so far… Fossil’s code is uncommonly well structured and fairly straightforward to

Re: [fossil-users] Workaround for the missing 'squash' command?

On May 11, 2016, at 4:24 PM, Marko Käning wrote: > > Is this deliberately missing functionality following fossil's mission to keep > all history? I suspect it’s more likely the case that fossil private branches are a subset of the functionality of regular branches,

[fossil-users] Behavior of private branches and merge --integrate

Hello, Recent discussion of private branches led me to discover one interesting detail about private branches. When merging in the private branch, Fossil does not add a P-card for the private branch, which seems sensible to me, however, it does add a T-card to close the private branch.

Re: [fossil-users] Workaround for the missing 'squash' command?

On Wed, May 11, 2016 at 6:24 PM, Marko Käning wrote: > How to achieve a git'ish squash when merging a (private) branch into trunk? > > Is this deliberately missing functionality following fossil's mission to > keep all history? > I think you are misunderstanding how a

Re: [fossil-users] fossil timeline on console quirk with ticket titles

On May 11, 2016, at 3:54 PM, Marko Käning wrote: > > Why does "fossil timeline" show HTML tags around ticket titles, like this: > > Ticket test > > ??? Because the command line implementation of “fossil ticket” is basically just dumping a subset of the

Re: [fossil-users] Workaround for the missing 'squash' command?

On Wed, May 11, 2016 at 4:24 PM, Marko Käning wrote: > How to achieve a git'ish squash when merging a (private) branch into trunk? > https://www.fossil-scm.org/xfer/doc/trunk/www/private.wiki seems to document this use case. You merge the private branch into a public

Re: [fossil-users] Workaround for the missing 'squash' command?

On Wed, May 11, 2016 at 8:26 PM, Andy Bradford wrote: > > What happens when you merge a private branch into trunk? You get a single commit that represents all the changes from the branch. This is unlike "git merge --fast-forward". (I don't know what just "git merge"

Re: [fossil-users] Workaround for the missing 'squash' command?

Thus said =?windows-1252?Q?Marko_K=E4ning?= on Thu, 12 May 2016 00:24:20 +0200: > How to achieve a git'ish squash when merging a (private) branch into > trunk? What happens when you merge a private branch into trunk? Thanks, Andy -- TAI64 timestamp: 40005733cde2

Re: [fossil-users] Unrecognized command-line option, or missing argument: --https

Ah, I didn't read the: "At this stage, the standalone server (e.g. "fossil server") does not support SSL." here: https://www.fossil-scm.org/xfer/doc/trunk/www/server.wiki. Still, online help should mention that as well, IMHO. Regards, Orzech Dnia 11 maja 2016 21:08 Piotr Orzechowski

[fossil-users] Workaround for the missing 'squash' command?

How to achieve a git'ish squash when merging a (private) branch into trunk? Is this deliberately missing functionality following fossil's mission to keep all history? Well, especially in case of a _private_ branch it might make sense to have such a feature: assume one wants to work locally on