Re: [fossil-users] How to list commits made so far?

2011-11-07 Thread Gilles
On Sun, 6 Nov 2011 16:22:36 +0400, Konstantin Khomoutov
flatw...@users.sourceforge.net wrote:
I think the meaning of these hashes is reversed: artifact is a particular 
version of a particular file according to [1],
 so the first hash here identifies the commit the artifact identified by the 
 second hash is a part of.
You can verify this simply by correlating the output of `fossil finfo`
with the output of `fossil timeline`.

Thanks for the info. Apparently, when running fossil finfo myfile,
the first hash identifies the whole commit (ie. all the files whose
changes were commited when running fossil commit) while the second
hash identifies the particular commit for that particular file:

C:\Projects\Project1fossil finfo Form1.vb
2011-11-05 [6a07f19e02] Code complete (user: Joe, artifact:
[9735460a2c])

C:\Projects\Project1fossil artifact 6a07f19e02
= List all the files affected by that commit

C:\Projects\Project1fossil artifact 9735460a2c
= List the state of the file when it was commited

One thing I'm not clear about, is how fossil timeline works: When
using -n 5, it shows three lines, while -n 10 shows five lines,
and -n 20 shows eleven :-/

http://fossil-scm.org/index.html/help?cmd=timeline

What does timeline show, really?

___
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] How to list commits made so far?

2011-11-07 Thread Konstantin Khomoutov
On Mon, 07 Nov 2011 15:10:12 +0100
Gilles gilles.gana...@free.fr wrote:

[...]
 One thing I'm not clear about, is how fossil timeline works: When
 using -n 5, it shows three lines, while -n 10 shows five lines,
 and -n 20 shows eleven :-/
 
 http://fossil-scm.org/index.html/help?cmd=timeline
 
 What does timeline show, really?
I can guess that's the effect of timeline defaulting to showing tickets
and wiki edits as well as commits.
What happens if you do
fossil timeline -t ci -n 20
?
___
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] How to list commits made so far?

2011-11-07 Thread Gilles
On Mon, 7 Nov 2011 18:37:23 +0400, Konstantin Khomoutov
flatw...@users.sourceforge.net wrote:
I can guess that's the effect of timeline defaulting to showing tickets
and wiki edits as well as commits.
What happens if you do
fossil timeline -t ci -n 20
?

Good idea, but still strange:

C:\Projects\Project1fossil timeline -n 5 -t ci
= Shows three commits

C:\Projects\Project1fossil timeline -n 10 -t ci
= Shows five commits

I only use the CLI to work with Fossil, and I don't use it for
ticketing.

Anyway, timeline answers my question about how to list commits,
although out of curiosity, I wonder why it doesn't show the number of
commits as expected.

___
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] How to list commits made so far?

2011-11-07 Thread Lluís Batlle i Rossell
On Mon, Nov 07, 2011 at 03:41:44PM +0100, Gilles wrote:
 On Mon, 7 Nov 2011 18:37:23 +0400, Konstantin Khomoutov
 flatw...@users.sourceforge.net wrote:
 I can guess that's the effect of timeline defaulting to showing tickets
 and wiki edits as well as commits.
 What happens if you do
 fossil timeline -t ci -n 20
 ?
 
 Good idea, but still strange:
 
 C:\Projects\Project1fossil timeline -n 5 -t ci
 = Shows three commits
 
 C:\Projects\Project1fossil timeline -n 10 -t ci
 = Shows five commits

'n' sets the maximum number of lines, iirc.
___
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] How to list commits made so far?

2011-11-07 Thread Gilles
On Mon, 7 Nov 2011 15:45:16 +0100, Lluís Batlle i Rossell
virik...@gmail.com wrote:
'n' sets the maximum number of lines, iirc.

This is not what is showing here. No matter what I count as lines, I
don't get five lines when I type -n 5:

C:\Projects\Project1fossil timeline -n 5 -t ci
=== 2011-11-05 ===
02:14:42 [6a07f19e02] *CURRENT* Code complete (user: Joe tags: trunk)
=== 2011-11-04 ===
13:02:18 [367bcfa41a] Some other comment (user: Joe tags: trunk)
=== 2011-11-03 ===
15:13:52 [492bc26bae] Some other comment (user: Joe tags: trunk)

___
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] How to list commits made so far?

2011-11-07 Thread Konstantin Khomoutov
On Mon, 7 Nov 2011 15:45:16 +0100
Lluís Batlle i Rossell virik...@gmail.com wrote:

  I can guess that's the effect of timeline defaulting to showing
  tickets and wiki edits as well as commits.
  What happens if you do
  fossil timeline -t ci -n 20
  ?
  
  Good idea, but still strange:
  
  C:\Projects\Project1fossil timeline -n 5 -t ci
  = Shows three commits
  
  C:\Projects\Project1fossil timeline -n 10 -t ci
  = Shows five commits
 
 'n' sets the maximum number of lines, iirc.
`fossil help timeline` from v1.20 I have installed mentions N twice:
1) In the command-line spec--that ?-n N? bit;
2) In the description text, where it's clearly placed in the context
   of check-ins.
___
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 and Jenkins?

2011-11-07 Thread Nolan Darilek
Just wondering if anyone has gotten Fossil to work with either Jenkins 
or Hudson for CI? My understanding is that these systems support a 
periodic poll mode that can compensate for the lack of hooks.


I'm about to start using Fossil more heavily in team projects, and in 
situations where I may wish to deploy via push. So I'm wondering if 
anyone has gotten this working with Jenkins, or indeed with any other 
CI. If there's a better fit for Fossil then I'd love to know about it.

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] Bug in commandline access to ticket reports

2011-11-07 Thread Marty Backe
We have 25 ticket reports.

The web access to any of these reports works fine.

Commandline Issues:

o When listing the reports via 'fossil ticket list report', only 22
reports appear. The Report Number begins with 0, then 1, 2 through 4 are
skipped, and then 5 through 25 are shown.
o Some of the missing reports can be shown when given the report title in
the 'fossil ticket show report title' command instead of using the
report number.
o The more recently created reports that don't show up in the 'list
report' command aren't even accessible via the 'fossil ticket show report
title' command.

So there appears to be issues with Fossil's commandline access to the
ticket reports when there are a lot of reports.

I'm using Fossil 1.20

___
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] How to list commits made so far?

2011-11-07 Thread Gilles
On Mon, 7 Nov 2011 19:18:44 +0400, Konstantin Khomoutov
flatw...@users.sourceforge.net wrote:
2) In the description text, where it's clearly placed in the context
   of check-ins.

I guess it would make more sense that -n stands for number of
check-in's, but it's not returning that number.

I updated from 1.19 to 1.20, and re-ran the command on my repo: -n 5
still doesn't return the last five check-in's. Maybe this is not what
the -n switch mean.

___
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] How to list commits made so far?

2011-11-07 Thread Martin Gagnon
On 2011-11-07, at 18:42, Ross Berteig r...@cheshireeng.com wrote:

 At 02:32 PM 11/7/2011, Gilles wrote:
 I guess it would make more sense that -n stands for number of
 check-in's, but it's not returning that number.
 
 I updated from 1.19 to 1.20, and re-ran the command on my repo:
 -n 5 still doesn't return the last five check-in's. Maybe this
 is not what the -n switch mean.
 
 Without examining the code, I've tried a couple of experiments in
 a repo of my own. It appears that the -n N option specifies a
 desired number of lines to output, but tests it only between
 complete timeline entries. Also, the lines containing only a date
 are not counted against N.
 
 So if your checkin comments are all short enough there are many
 of them per day, then you will have about two lines per entry and
 you can estimate the number of entries printed for -n N to be
 N/2. However, if your entries are more explanatory or occur at
 one per day or less then you will get fewer entries.
 
 If your comments are typically very verbose or vary a lot in
 length, then the number of output lines may bear very little
 relationship to the number of items output.
 
 The Timeline tab in the web ui appears to count actual entries
 not length. I'd respectfully suggest that since trimming text to
 a set number of lines is an easy operation but counting entries
 is not, the fossil timeline command's -n option should count
 entries and not try (and fail) to count lines.
 

According to fossil help timeline -n specify the number of checkins.

-- 
Martin G.
___
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] How to list commits made so far?

2011-11-07 Thread Martin Gagnon
On Tue, Nov 08, 2011 at 01:31:21AM +0100, Gilles wrote:
 On Mon, 07 Nov 2011 15:42:35 -0800, Ross Berteig
 r...@cheshireeng.com wrote:
 So if your checkin comments are all short enough there are many
 of them per day, then you will have about two lines per entry and
 you can estimate the number of entries printed for -n N to be
 N/2. However, if your entries are more explanatory or occur at
 one per day or less then you will get fewer entries.
 
 As I'm still learning about Fossil, and use Fossil mostly to track
 changes made to documents and small development projects, the comments
 I used to learn about Fossil are typically one-line long, and I only
 commited changes a couple of times a day, so my experience doesn't
 match real-life use.
 
 But I agree with the other comments that -n should return the n
 last check-in's/commits.
 

I've just investigate a little bit. On web ui, parameter work as
expected for the n parameter and show number of checkins. 

e.g.: 
http://www.fossil-scm.org/index.html/timeline?n=5

Will show 5 last checkins.

But for the same repository (my clone), using command line I get only 3 
checkins:


$ fossil timeline -n 5
=== 2011-11-07 ===
07:07:33 [5905232d45] fossil already provides compatibility wrappers for
 dirent and struct timeval (user: steveb tags: jimtcl)
05:51:20 [b6270d665b] Update Jim Tcl to build with MSVC (user: steveb tags:
 jimtcl)
03:39:21 [7ee228fe6a] Remove HAVE_MKDIR_ONE_ARG define when compiling Jim as
 it will now be defined in the C file itself. (user: mistachkin tags:
 jimtcl)


Looking at the code, the timeline_cmd() seems to search for n last
checkins but call at the end:  print_timeline() which take the n as
second argument. The problem is that the second argument of print_timeline() is
used to limit the number of line, not number of checkins.


-- 
Martin G.
___
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] How to list commits made so far?

2011-11-07 Thread Dmitry Chestnykh
On Mon, 07 Nov 2011 15:42:35 -0800 Ross Berteig r...@cheshireeng.com
wrote:

 At 02:32 PM 11/7/2011, Gilles wrote:
  I guess it would make more sense that -n stands for number of
  check-in's, but it's not returning that number.
  
  I updated from 1.19 to 1.20, and re-ran the command on my repo:
  -n 5 still doesn't return the last five check-in's. Maybe this
  is not what the -n switch mean.
 
 Without examining the code, I've tried a couple of experiments in
 a repo of my own. It appears that the -n N option specifies a
 desired number of lines to output, but tests it only between
 complete timeline entries. Also, the lines containing only a date
 are not counted against N.

Here's a bug report from last November, with a patch:

http://www.fossil-scm.org/index.html/tktview?name=3e58b8ceaf

-- 
Dmitry Chestnykh
http://www.codingrobots.com
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] Cloning, syncing via ssh appears to hang...

2011-11-07 Thread Matt Welland
I'm on Linux and commands such as the following appear to hang:

fossil clone ssh://u...@host.domain.tld/path/repo.fossil repo.fossil

I have ssh with keys (passwordless login) working fine.

How to debug this?

fossil version
This is fossil version 1.19 [6517b5c857] 2011-09-01 18:25:19 UTC
___
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] Cloning, syncing via ssh appears to hang...

2011-11-07 Thread Eduardo Tongson
On Tue, Nov 8, 2011 at 4:00 AM, Matt Welland estifo...@gmail.com wrote:
 I'm on Linux and commands such as the following appear to hang:

 fossil clone ssh://u...@host.domain.tld/path/repo.fossil repo.fossil

 I have ssh with keys (passwordless login) working fine.

 How to debug this?

 fossil version
 This is fossil version 1.19 [6517b5c857] 2011-09-01 18:25:19 UTC



Adding -v to the ssh command is a good start. Set it with `fossil
settings ssh-command`

Good luck.
___
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] Cloning, syncing via ssh appears to hang...

2011-11-07 Thread Matt Welland
On Mon, Nov 7, 2011 at 9:21 PM, Eduardo Tongson propol...@gmail.com wrote:

 On Tue, Nov 8, 2011 at 4:00 AM, Matt Welland estifo...@gmail.com wrote:
  I'm on Linux and commands such as the following appear to hang:
 
  fossil clone ssh://u...@host.domain.tld/path/repo.fossil repo.fossil
 
  I have ssh with keys (passwordless login) working fine.
 
  How to debug this?
 
  fossil version
  This is fossil version 1.19 [6517b5c857] 2011-09-01 18:25:19 UTC
 
 

 Adding -v to the ssh command is a good start. Set it with `fossil
 settings ssh-command`


Here is what I get:

debug: SshConfig/sshconfig.c:3116/ssh2_parse_config_ext: Metaconfig parsing
stopped at line 3.
debug: SshConfig/sshconfig.c:3417/ssh_config_read_file_ext: Read 4 params
from config file.
debug: SshUnixUserFiles/sshunixuserfiles.c:409/ssh_read_client_configs:
Found user config file '/path/to/my/home/dir/.ssh2/ssh2_config'
debug: SshConfig/sshconfig.c:3116/ssh2_parse_config_ext: Metaconfig parsing
stopped at line 2.

This is fsecure ssh (I think?)
 ssh -h
ssh: Reflection for Secure IT 6.1.2.1 (build 3005) on x86_64-suse-linux-gnu
(64-bit)


Good luck.
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users