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 timeline
gives by default (unless one uses the "-t ci" option). So, I thought 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] FINFO suggestion
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
files.
I dream about that feature since the beginning I use fossil.
Alternatively, I think modifying "timeline" command/webpage to have the
capability to limit it scope to one subdirectory would be nice. Imagine
a team where one is dedicated to the documentation and only work in
doc/, when he look at the timeline to follow his work, it's hard to
track changes that was made inside doc/ directory. (especially if his
college commit a lot more than him inside src/).
<snip>
But with the timeline approach, it would an easy add-on I guess.
<snip>
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
