Re: [fossil-users] Ticket system -- blockers

2013-10-07 Thread Richard Hipp
On Sun, Oct 6, 2013 at 9:55 PM, Joseph R. Justice jayare...@gmail.comwrote: During the push, it is noticed that R(N) says bug B2 is closed while R' says it is open and blocked by B1 (and that A specified the block), which is open both in R' and R(N). N should be notified of this as it is

[fossil-users] Incompatible and undocumented output change between 1.24 and 1.27

2013-10-07 Thread Stefan Bellon
Hi all, we've been using Fossil 1.24 as storage system for generated files in our environment for quite some time now. Recently, we decided to update from 1.24 to 1.27. When deciding whether to do the update or not, I read through all the ChangeLogs on the website and I made sure that all

Re: [fossil-users] Incompatible and undocumented output change between 1.24 and 1.27

2013-10-07 Thread Richard Hipp
On Mon, Oct 7, 2013 at 9:12 AM, Stefan Bellon sbel...@sbellon.de wrote: Previously, with fossil 1.24, the third column of the annotate output was the author who did the most recent change to the line. Now, with fossil 1.27, it's just the line number being displayed. First of all, this

Re: [fossil-users] http-proxy + https

2013-10-07 Thread Jan Danielsson
Hello, There's a jan-httpsproxytunnel (work-in-progress) branch with support for tunneling https over a http proxy. I have done a few https-over-http-proxy clones, and I also made some https (without proxy) clones to see if I broke anything. I have however not done extensive testing, so ..

Re: [fossil-users] Incompatible and undocumented output change between 1.24 and 1.27

2013-10-07 Thread Stefan Bellon
On Mon, 07 Oct, Richard Hipp wrote: On Mon, Oct 7, 2013 at 9:12 AM, Stefan Bellon sbel...@sbellon.de wrote: Previously, with fossil 1.24, the third column of the annotate output was the author who did the most recent change to the line. Now, with fossil 1.27, it's just the line number

Re: [fossil-users] Incompatible and undocumented output change between 1.24 and 1.27

2013-10-07 Thread Stephan Beal
On Mon, Oct 7, 2013 at 4:26 PM, Stefan Bellon sbel...@sbellon.de wrote: On Mon, 07 Oct, Richard Hipp wrote: Most people are more interested in the fact that the line changed. The identity of the editor is of secondary importance, I beg to differ strongly. The command is called annotate and

Re: [fossil-users] Incompatible and undocumented output change between 1.24 and 1.27

2013-10-07 Thread Richard Hipp
On Mon, Oct 7, 2013 at 10:26 AM, Stefan Bellon sbel...@sbellon.de wrote: The username was therefore removed from the primary display in order to reduce the amount of clutter and to make the output easier for humans to read. Was this discussed on the mailing list and I missed it? Or was

Re: [fossil-users] Incompatible and undocumented output change between 1.24 and 1.27

2013-10-07 Thread sky5walk
Fossil has never guaranteed specific output for any given command, ...~ The output of any and all commands is subject to change without notice between any given versions. As a general rule, whoever hacks the feature determines the output format. i would go so far as to say that Fossil's output has

Re: [fossil-users] Ticket system -- blockers

2013-10-07 Thread Matt Welland
Applying constraints as receiver end filtering could be very useful and I think it could fit the sync model if not needed blobs were not necessarily dropped but a record was kept so that they wouldn't be sync'd and they are kept out of the list of blobs. Essentially something similar to what the

Re: [fossil-users] Incompatible and undocumented output change between 1.24 and 1.27

2013-10-07 Thread Stephan Beal
On Mon, Oct 7, 2013 at 5:27 PM, sky5w...@gmail.com wrote: I guess the library interface is the target moving forward instead of forcing standardized output? Good question. Ideally the library will produce _no_ text output other than the propagation of error messages from lower levels (e.g.

Re: [fossil-users] Incompatible and undocumented output change between 1.24 and 1.27

2013-10-07 Thread sky5walk
Very nice. My initial thoughts were to reproduce the existing fossil cmds but you are correct that this should not be the library's sole purpose. On Mon, Oct 7, 2013 at 11:59 AM, Stephan Beal sgb...@googlemail.com wrote: On Mon, Oct 7, 2013 at 5:27 PM, sky5w...@gmail.com wrote: I guess the

Re: [fossil-users] Incompatible and undocumented output change between 1.24 and 1.27

2013-10-07 Thread Stephan Beal
On Mon, Oct 7, 2013 at 7:40 PM, Jakob Eriksson ja...@aurorasystems.euwrote: Of course you have no obligations but I think Fossil is getting more popular. That means you will break more people's scripts and expectations. Just something to consider. OTOH, anyone who takes the time to ask on

Re: [fossil-users] Incompatible and undocumented output change between 1.24 and 1.27

2013-10-07 Thread Jakob Eriksson
For each person taking that time, there will be 1000 more not taking that time. That said, you are intentionally leaving a gap between human interaction and a library, and that gap is classic Unix scripting with stdout and stdin. Of course one could build a stable text interface automation

Re: [fossil-users] Incompatible and undocumented output change between 1.24 and 1.27

2013-10-07 Thread Andreas Kupries
On Mon, Oct 7, 2013 at 6:38 AM, Richard Hipp d...@sqlite.org wrote: On Mon, Oct 7, 2013 at 9:12 AM, Stefan Bellon sbel...@sbellon.de wrote: But more severely, the information who changed the line is now not present anymore at all. Most people are more interested in the fact that the line

Re: [fossil-users] Incompatible and undocumented output change between 1.24 and 1.27

2013-10-07 Thread Richard Hipp
On Mon, Oct 7, 2013 at 1:40 PM, Jakob Eriksson ja...@aurorasystems.euwrote: Of course you have no obligations but I think Fossil is getting more popular. That means you will break more people's scripts and expectations. Just something to consider. There is tension between preserving

Re: [fossil-users] Incompatible and undocumented output change between 1.24 and 1.27

2013-10-07 Thread Ron Wilson
On Mon, Oct 7, 2013 at 2:37 PM, Andreas Kupries andre...@activestate.comwrote: On Mon, Oct 7, 2013 at 6:38 AM, Richard Hipp d...@sqlite.org wrote: Most people are more interested in the fact that the line changed. The identity of the editor is of secondary importance, Not when you have

Re: [fossil-users] Incompatible and undocumented output change between 1.24 and 1.27

2013-10-07 Thread Andreas Kupries
On Mon, Oct 7, 2013 at 12:18 PM, Ron Wilson ronw.m...@gmail.com wrote: On Mon, Oct 7, 2013 at 2:37 PM, Andreas Kupries andre...@activestate.com wrote: (*) With bisect we have the change, and this know who made it. However sometimes it is possible to determine a problematic line without

Re: [fossil-users] Incompatible and undocumented output change between 1.24 and 1.27

2013-10-07 Thread Matt Welland
Losing the username in annotate command line is a big hit for me. I don't understand why that would be removed. Is this driven by Windows users who are stuck with limited terminal width? You could shave off some characters by only printing the first 4 letters of the node id. Also the : at the end

Re: [fossil-users] Incompatible and undocumented output change between 1.24 and 1.27

2013-10-07 Thread Ron Wilson
On Mon, Oct 7, 2013 at 3:54 PM, Matt Welland estifo...@gmail.com wrote: Losing the username in annotate command line is a big hit for me. I don't understand why that would be removed. From Richard's comment, I surmise he (and others) mostly use the web version of annotate, where clicking on

Re: [fossil-users] Anecdote regarding permissions tracking in Fossil

2013-10-07 Thread Joseph R. Justice
On Mon, Sep 23, 2013 at 7:05 AM, Alaric Snell-Pym ala...@snell-pym.org.ukwrote: I've written a backup/archival tool based on content-addressible storage, and a common question people ask is So why don't I just put my home directory/entire filesystem in git, then?, and I have to raise this

Re: [fossil-users] Ticket system -- blockers

2013-10-07 Thread Ron Wilson
On Mon, Oct 7, 2013 at 11:31 AM, Matt Welland estifo...@gmail.com wrote: Applying constraints as receiver end filtering could be very useful and I think it could fit the sync model if not needed blobs were not necessarily dropped but a record was kept so that they wouldn't be sync'd and they

Re: [fossil-users] Anecdote regarding permissions tracking in Fossil

2013-10-07 Thread Matt Welland
On Mon, Oct 7, 2013 at 3:27 PM, Joseph R. Justice jayare...@gmail.comwrote: On Mon, Sep 23, 2013 at 7:05 AM, Alaric Snell-Pym ala...@snell-pym.org.uk wrote: I've written a backup/archival tool based on content-addressible storage, and a common question people ask is So why don't I just put