Thus said Jan Danielsson on Mon, 11 Apr 2016 17:06:02 +0200:
>Short version: What's the best way to determine if a repository has
> changed?
Define ``changed.'' ;-)
If all you care about are artifacts:
fossil dbstat -R repo.fossil | grep artifact-count | awk '{ print $2 }'
If that number
On 11/04/16 17:17, Stephan Beal wrote:
[---]
>>Is there a timestamp for when artifacts where locally added to the
>> repository? (I'm not overly concerned with configuration changes and
>> such; it's detecting checkins, tickets and other artifact changes that's
>> important).
>
> rcvfrom
On Mon, Apr 11, 2016 at 8:37 PM, Ross Berteig wrote:
>
> "fossil":"9c65b5432e4aeecf3556e5550c338ce93fd861cc",
> "timestamp":1460399740,
>
...
"timestamp":1460254449,
reminder to self: add a "iso8601" property for
On 4/11/2016 8:17 AM, Stephan Beal wrote:
On Mon, Apr 11, 2016 at 5:06 PM, Jan Danielsson
> wrote:
The most obvious method would be to do roughly what the timeline
does
and find the latest modification on the
I submitted a patch to create a --mail-quiet option for update that is
quiet unless a change has happened. But it never made its way into trunk
(even though I sent the copyright form to Rich)
The comment for it reads:
The -m or --mail-quiet option suppresses status info unless there was
some
On Mon, Apr 11, 2016 at 5:06 PM, Jan Danielsson
wrote:
>The most obvious method would be to do roughly what the timeline does
> and find the latest modification on the timeline, but this wouldn't work
> (since it would miss modifications from older checkins (say a
Hello,
Short version: What's the best way to determine if a repository has
changed?
I have two systems which are sync'd in a cronjob. On one of the
systems I run a cronjob which should take action only if the repository
was changed. Before there were two systems I simply used mtime on
7 matches
Mail list logo