On Mon, 07 Nov 2011 15:42:35 -0800 Ross Berteig
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"
On Tue, Nov 08, 2011 at 01:31:21AM +0100, Gilles wrote:
> On Mon, 07 Nov 2011 15:42:35 -0800, Ross Berteig
> 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 prin
On Mon, 07 Nov 2011 15:42:35 -0800, Ross Berteig
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 explana
On 2011-11-07, at 18:42, Ross Berteig 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
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 t
On Mon, 7 Nov 2011 19:18:44 +0400, Konstantin Khomoutov
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
On Mon, 7 Nov 2011 15:45:16 +0100
Lluís Batlle i Rossell 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:
> >
> >
On Mon, 7 Nov 2011 15:45:16 +0100, Lluís Batlle i Rossell
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\Project1>fossil timeline -n 5 -t ci
=== 2011-11-05 ===
02:14:4
On Mon, Nov 07, 2011 at 03:41:44PM +0100, Gilles wrote:
> On Mon, 7 Nov 2011 18:37:23 +0400, Konstantin Khomoutov
> 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
> >?
On Mon, 7 Nov 2011 18:37:23 +0400, Konstantin Khomoutov
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\Project1>fossil timeline -
On Mon, 07 Nov 2011 15:10:12 +0100
Gilles 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
On Sun, 6 Nov 2011 16:22:36 +0400, Konstantin Khomoutov
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
On Sun, 6 Nov 2011 09:28:51 -0500
Martin Gagnon wrote:
> > wrote: Is there a command that I could run to list all the commits,
> > and for each, would show which files were part of the commit?
> > fossil timeline -showfiles -n 10
> >
> > The -n parameter is kind of a kludge there. By default
On 2011-11-06, at 07:09, Stephan Beal wrote:
> On Sun, Nov 6, 2011 at 11:19 AM, Gilles wrote:
> Is there a command that I could run to list all the commits, and for
> each, would show which files were part of the commit?
>
>
> fossil timeline -showfiles -n 10
>
> The -n parameter is kind
On Sun, 06 Nov 2011 11:19:08 +0100
Gilles wrote:
> I'd like to check something about how Fossil works.
>
> When I run "fossil commit", it saves the changes made to all the files
> that are monitored (ie. that have been added to the repository).
One usually uses the term "tracked" (instead of "mo
On Sun, Nov 6, 2011 at 11:19 AM, Gilles wrote:
> Is there a command that I could run to list all the commits, and for
> each, would show which files were part of the commit?
>
>
fossil timeline -showfiles -n 10
The -n parameter is kind of a kludge there. By default there is a limit to
how ma
Hello,
I'd like to check something about how Fossil works.
When I run "fossil commit", it saves the changes made to all the files
that are monitored (ie. that have been added to the repository).
When I run "fossil finfo" on a file, it shows two hashes:
C:\Projects\Project1>fossil finfo Form1.vb
17 matches
Mail list logo
