Re: [fossil-users] Getting time of last repository change

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

Re: [fossil-users] feature implemented or suggestion for stash

Thus said Stephan Beal on Mon, 11 Apr 2016 17:20:22 +0200: > If i understand correctly, that's what fossil intends branches to be > used for. stashes are generally not intended for long-term storage. > They're intended primarily for "oops, i need to quickly do something > over in this

Re: [fossil-users] Getting time of last repository change

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

Re: [fossil-users] Getting time of last repository change

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

Re: [fossil-users] Getting time of last repository change

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

Re: [fossil-users] feature implemented or suggestion for stash

all my samples include messages. If that's the point then I could add all the 'interface' I need into the -m flag including console codes to draw boxes and stuff. 2016-04-11 13:15 GMT-03:00 Stephan Beal : > On Mon, Apr 11, 2016 at 5:56 PM, fran

Re: [fossil-users] feature implemented or suggestion for stash

forget the command line cases. The checkout was a children of the checkout I was requesting to purge. 2016-04-11 13:45 GMT-03:00 fran : > Whats the effect if I use the --integrate option? > > 2016-04-11 13:17 GMT-03:00 Tony Papadimitriou : > >> Once you’re

Re: [fossil-users] feature implemented or suggestion for stash

Whats the effect if I use the --integrate option? 2016-04-11 13:17 GMT-03:00 Tony Papadimitriou : > Once you’re ready to move the changes to a normal branch you simply merge > (but without the –integrate option or else the purge won’t work correctly), > and then purge the private

Re: [fossil-users] feature implemented or suggestion for stash

I don’t know if this will be of any help, but I moved away from using stash altogether for pretty much the same reasons you mention, plus one very important one for me that I don’t like about the stash: the content of the stash only stays on the current PC while I wanted it to follow the repo

Re: [fossil-users] feature implemented or suggestion for stash

On Mon, Apr 11, 2016 at 5:56 PM, fran wrote: > The current listing displays > 1: [199b53d1d70361] on 2016-03-25 05:08:21 > > To the new user this says "something 199b53d1d70361 got 'commited' on such > date"... > Have you tried using the -m option? [stephan@host:~]$

Re: [fossil-users] Getting time of last repository change

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

Re: [fossil-users] feature implemented or suggestion for stash

On Mon, Apr 11, 2016 at 4:28 PM, fran wrote: > I never realized the presented uuid was actually the baseline. > Stephan Beal said he wasn't even aware of the 'stash goto' > command! And I (noob user) couldn't understand what > the 'goto' would do. > There are _lots_ of

Re: [fossil-users] Getting time of last repository change

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

[fossil-users] Getting time of last repository change

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

[fossil-users] feature implemented or suggestion for stash

the stash could give more info about the baseline checkout. It currently shows just the checkout uuid. I never realized the presented uuid was actually the baseline. Stephan Beal said he wasn't even aware of the 'stash goto' command! And I (noob user) couldn't understand what the 'goto' would do.

Re: [fossil-users] Fossil local repository no more able to push checkin (error 141)

On Sun, 9 Apr 2016, Andy Bradford wrote: Thus said =?ISO-8859-15?Q?=C9tienne_Deparis?= on Fri, 08 Apr 2016 09:36:01 +0200: Thank you for your quick reply. I did not think about bash related problem. I found interesting stuff when searching about bash and error code 141: it seems it is