Re: Request for new /closeonend command parameter for no changes
Although I am still missing this feature but as a workaround I was able to make a script using AutoHotkey to automatically close the update window if there were no changes. On Monday, February 26, 2018 at 9:58:01 AM UTC+1, Balázs wrote: > > Than maybe the "no changes at all" is misleading. > The point is not to detect if there is any kind of update. > I would just like to see if there is any change that needs review. > When I see that there are no updated files/folders under a specified > repository, I know there is nothing to review so the log window can be > closed. > > > On Thursday, February 22, 2018 at 7:33:33 PM UTC+1, Stefan wrote: >> >> That's not really feasible. For example if you run "update", even if >> there are no file content updates, the working copy is still updated >> internally: the revision to which it was updated is stored on the folder >> itself, so there's still 'a change'. >> > -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/812f2c83-8501-4463-a09d-2e0159697510%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Request for new /closeonend command parameter for no changes
Than maybe the "no changes at all" is misleading. The point is not to detect if there is any kind of update. I would just like to see if there is any change that needs review. When I see that there are no updated files/folders under a specified repository, I know there is nothing to review so the log window can be closed. On Thursday, February 22, 2018 at 7:33:33 PM UTC+1, Stefan wrote: > > That's not really feasible. For example if you run "update", even if there > are no file content updates, the working copy is still updated internally: > the revision to which it was updated is stored on the folder itself, so > there's still 'a change'. > -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/af14c76d-e3d7-47d2-a38f-5b83d877f46a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Request for new /closeonend command parameter for no changes
That's not really feasible. For example if you run "update", even if there are no file content updates, the working copy is still updated internally: the revision to which it was updated is stored on the folder itself, so there's still 'a change'. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/f34aa8c2-8c8a-4b88-bf76-aa37b77fdf1b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Request for new /closeonend command parameter for no changes
I would like to propose a new condition for the /closeonend automation parameter: auto close if there are no changes at all (list is empty) -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/72611e46-342d-4a4a-a22c-b9b668ec5503%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
