FINFO (Usage: fossil finfo ?OPTIONS? FILENAME) is one of the most useful
features of fossil as it accepts a filename and provides its history of changes
(unfortunately, it does not follow possible file renames, but that’s another
issue).
What I would like is to have the possibility to also
On Fri, Oct 17, 2014 at 8:34 AM, Tony Papadimitriou to...@acm.org wrote:
Would that be too much programming effort to add? I.e., check if
‘filename’ is a directory and in that case return FINFO for all associated
files.
If it weren't for the -status and -print options, it would require
On Fri, Oct 17, 2014 at 10:16 AM, Tony Papadimitriou to...@acm.org wrote:
Not being sure I understood your approach completely, and without
knowing fossil’s internals, but knowing that it uses SQL for a lot of its
work, I think that mostly the related SQL would have to change.
I believe a
On Fri, Oct 17, 2014 at 09:59:26AM +0200, Stephan Beal wrote:
On Fri, Oct 17, 2014 at 8:34 AM, Tony Papadimitriou to...@acm.org wrote:
Would that be too much programming effort to add? I.e., check if
‘filename’ is a directory and in that case return FINFO for all associated
since
FINFO already only deals with file edits (ignoring all the rest), this would
be the right place to do it with less changes. But, I don't know.
-Original Message-
From: Martin Gagnon
Sent: Friday, October 17, 2014 4:56 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users
On Fri, Oct 17, 2014 at 10:17 AM, to...@acm.org wrote:
I guess the timeline equivalent would work, too!
Please try out the change on the cmdline-timeline-enhancement branch and
see if it works for you.
--
D. Richard Hipp
d...@sqlite.org
___
On Fri, Oct 17, 2014 at 05:17:24PM +0300, to...@acm.org wrote:
snip
I guess the timeline equivalent would work, too! However, I'd be
more interested in being able to see just the code changes (i.e.,
check-ins) and not all the 'noise' about wiki edits, tickets, tags,
etc which the
On Fri, Oct 17, 2014 at 11:32:27AM -0400, Richard Hipp wrote:
On Fri, Oct 17, 2014 at 10:17 AM, to...@acm.org wrote:
I guess the timeline equivalent would work, too!
Please try out the change on the cmdline-timeline-enhancement branch
and see if
it works for you.
Nice,
On Fri, Oct 17, 2014 at 12:01 PM, Martin Gagnon eme...@gmail.com wrote:
I guess the next step is to have that feature on the /timeline web page,
and may be a timeline link beside each directory in the /tree web
page..
That's harder to do because the graph is disjoint when you skip
On Fri, Oct 17, 2014 at 12:05:36PM -0400, Richard Hipp wrote:
On Fri, Oct 17, 2014 at 12:01 PM, Martin Gagnon eme...@gmail.com wrote:
I guess the next step is to have that feature on the /timeline web page,
and may be a timeline link beside each directory in the /tree web
tim filename” I get the history of the given filename.
Thanks for the change.
From: Richard Hipp
Sent: Friday, October 17, 2014 6:32 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] FINFO suggestion
On Fri, Oct 17, 2014 at 10:17 AM, to...@acm.org wrote:
I guess the timeline
One more problem I see is that it sometimes shows the same timeline entry
multiple times in a row (same SHA1 and description)
From: to...@acm.org
Sent: Friday, October 17, 2014 7:51 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] FINFO suggestion
I did a quick try
SCM user's discussion
Subject: Re: [fossil-users] FINFO suggestion
One more problem I see is that it sometimes shows the same timeline entry
multiple times in a row (same SHA1 and description)
From: to...@acm.org
Sent: Friday, October 17, 2014 7:51 PM
To: Fossil SCM user's discussion
Subject
On Fri, Oct 17, 2014 at 08:57:50PM +0300, to...@acm.org wrote:
An observation related to the last problem. The identical multiple
entries seem to match the number of files that have changed in that
subdirectory. So, if three files changed, the same timeline entry
appears three times.
14 matches
Mail list logo
