It is 3pm in the afternoon and I was doing my usual task writing some code. I accidentally came across an interesting code that actually saves your processing power when implemented. Let me show you my findings.

I’m using PHP by the way to code a project that handles several processes at a time. I stumbled on this funny situation where you have to code a “sleep” function that runs a pause in an execution momentarily and then resumes. Putting this in real life experience, you have to take a break some times even if you got a ton of work at least get a minute or two to get yourself together then start working again.

Ok now here’s the scenario, I put a sleep method and this is what happens...

the code:

what's happening:

Since I put a sleep method, the CPU is quite calm (at least for me)

If you remove the sleep method this is what happens...

the code:

what's happening:

When i removed the sleep method the CPU's processing became quite hectic and that's because it is doing tasks continuously.

So, resting doesn’t only apply in real life but also our machines can benefit from it! Keep in mind that sleep… is also important.

I've been looking for ways on how to make svn commits require a message just before they get committed. A problem is that some developers make a mistake by making empty commits making the reason of the commit unknown. I found this code via google and I wanted to share it.

This has been tested working in VisualSVN Server.

1. open your visual svn server

2. right click on a repository then click properties

3. on the hooks tab, edit the Pre-commit hook then paste the code:

@echo off
::    
:: Stops commits that have empty log messages.
::

@echo off

setlocal

rem Subversion sends through the path to the repository and transaction id
set REPOS=%1
set TXN=%2

rem check for an empty log message
svnlook log %REPOS% -t %TXN% | findstr . > nul
if %errorlevel% gtr 0 (goto err) else exit 0

:err
echo. 1>&2
echo Your commit has been blocked because you didn't give any log message 1>&2
echo Please write a log message describing the purpose of your changes and 1>&2
echo then try committing again. -- Thank you 1>&2
exit 1

4. click "ok", then "ok" 

If you happen to find a better script than this, please let me know.