[fossil-users] Enhancement: commit and close merged leaf

2013-07-10 Thread Harald Oehlmann
Following hint by Andreas: https://groups.google.com/forum/#!topic/comp.lang.tcl/JwSNrTYgjTk the following enhancement to fossil is proposed: with fossil commit, there should be a possibility (parameter) to close a merged branch. So here is a current typical session to merge a branch to trunk:

[fossil-users] SSH client updates.

2013-07-10 Thread Andy Bradford
Folks, As I mentioned before, I've been attempting some modifications to the fossil SSH URL handling. I'm at a point where I could use some feedback regarding the previous method for handling SSH. Originally, fossil would fork an SSH connection and then communicate with the remote shell

Re: [fossil-users] Enhancement: commit and close merged leaf

2013-07-10 Thread Stephan Beal
On Wed, Jul 10, 2013 at 9:37 AM, Harald Oehlmann harald.oehlm...@elmicron.de wrote: 1) fossil open repo 2) fossil merge branch 3) fossil commit 4) And then, I go to the web interface and set the closed leaf property of the branch. The last step would be natural for me to de done with the

Re: [fossil-users] Enhancement: commit and close merged leaf

2013-07-10 Thread Harald Oehlmann
Am 10.07.2013 11:51, schrieb Stephan Beal: On Wed, Jul 10, 2013 at 9:37 AM, Harald Oehlmann harald.oehlm...@elmicron.de mailto:harald.oehlm...@elmicron.de wrote: 1) fossil open repo 2) fossil merge branch 3) fossil commit 4) And then, I go to the web interface and set the

Re: [fossil-users] SSH client updates.

2013-07-10 Thread Stephan Beal
On Wed, Jul 10, 2013 at 9:51 AM, Andy Bradford amb-fos...@bradfords.orgwrote: ... Is there value in keeping this old method? I personally don't see any, but then I don't have the background to know why it was done this way. If i'm not sorely mistaken, the current approach was done

Re: [fossil-users] Enhancement: commit and close merged leaf

2013-07-10 Thread Stephan Beal
On Wed, Jul 10, 2013 at 11:57 AM, Harald Oehlmann harald.oehlm...@elmicron.de wrote: Am 10.07.2013 11:51, schrieb Stephan Beal: ... Closing at merging is also not ideal because it often happens that a merge gets tossed out in the process of trying to fix conflicts (very often i have

Re: [fossil-users] Enhancement: commit and close merged leaf

2013-07-10 Thread Jan Nijtmans
2013/7/10 Stephan Beal sgb...@googlemail.com: i might have over-thought that problem: closing on merge probably isn't a problem here because if the leaf is closed that doesn't hinder us at all. Closing a leaf keeps us from committing to it, but not from pulling from it. To me closing at merge

Re: [fossil-users] Enhancement: commit and close merged leaf

2013-07-10 Thread Stephan Beal
On Wed, Jul 10, 2013 at 4:56 PM, Jan Nijtmans jan.nijtm...@gmail.comwrote: 2013/7/10 Stephan Beal sgb...@googlemail.com: To me closing at merge time sounds like the overall easier approach (but i'm very possibly ignoring/missing details/complications which i'm hoping another list member

[fossil-users] Hierarchical tags in Embedded Documentation

2013-07-10 Thread ST
Hi, is it possible to mark embedded documentation pages with hierarchical tags, like - fruit, banana and then list all pages that belong to the tags? If such feature is not present - may I ask to implement it? Thank you. ST ___ fossil-users mailing

Re: [fossil-users] Hierarchical tags in Embedded Documentation

2013-07-10 Thread Stephan Beal
On Wed, Jul 10, 2013 at 6:05 PM, ST smn...@gmail.com wrote: is it possible to mark embedded documentation pages with hierarchical tags, like - fruit, banana and then list all pages that belong to the tags? Fossil doesn't support tags at the _file_ level (not sure why not?) but at the checkin

Re: [fossil-users] SSH client updates.

2013-07-10 Thread Martin Gagnon
On Wed, Jul 10, 2013 at 01:51:05AM -0600, Andy Bradford wrote: Folks, As I mentioned before, I've been attempting some modifications to the fossil SSH URL handling. I'm at a point where I could use some feedback regarding the previous method for handling SSH. [snip] I like the idea

Re: [fossil-users] SSH client updates.

2013-07-10 Thread Rene
On 2013-07-10 21:31, Martin Gagnon wrote: On Wed, Jul 10, 2013 at 01:51:05AM -0600, Andy Bradford wrote: Folks, As I mentioned before, I've been attempting some modifications to the fossil SSH URL handling. I'm at a point where I could use some feedback regarding the previous method for

Re: [fossil-users] SSH client updates.

2013-07-10 Thread Martin Gagnon
On Wed, Jul 10, 2013 at 10:32:26PM +0200, Rene wrote: On 2013-07-10 21:31, Martin Gagnon wrote: On Wed, Jul 10, 2013 at 01:51:05AM -0600, Andy Bradford wrote: Folks, As I mentioned before, I've been attempting some modifications to the fossil SSH URL handling. I'm at a point where I

Re: [fossil-users] SSH client updates.

2013-07-10 Thread Martin Gagnon
On Wed, Jul 10, 2013 at 05:24:29PM -0400, Martin Gagnon wrote: On Wed, Jul 10, 2013 at 10:32:26PM +0200, Rene wrote: On 2013-07-10 21:31, Martin Gagnon wrote: On Wed, Jul 10, 2013 at 01:51:05AM -0600, Andy Bradford wrote: Folks, As I mentioned before, I've been attempting some

Re: [fossil-users] SSH client updates.

2013-07-10 Thread Andy Bradford
Thus said Martin Gagnon on Wed, 10 Jul 2013 17:50:40 -0400: Sorry, *my* mistake.. I didn't notice the new version of the patch on latest Andy Bradford email. My test was made with the previous patch. Not a problem. I should probably setup a fossil clone that can be accessed, rather

Re: [fossil-users] SSH client updates.

2013-07-10 Thread Andy Bradford
Thus said Martin Gagnon on Wed, 10 Jul 2013 17:50:40 -0400: Work fine now.. sorry for the noise.. Speaking of noise, time to add a little more (because my original email wasn't quite long enough). The new options that I've added are not yet fully documented in the usage/help (not having