Viewing profile — prashanthellina

That is Gold! Implementing the functionality in shell itself was what I considered first however I needed two things 1. Make it work on OSX 2. Use a lock file to prevent multiple i…

The memory "leak" persists across restarts of my process. That is what beats me. If memory were leaking while the process was alive and was reclaimed by the OS upon killing the pro…

Thank you! I tried hard to keep the code very simple sacrificing some 20%-scenario requirements (such as automatic conflict resolution). I am using this to synchronize my Markdown …

No apologies required! Thanks for taking the time to post the links. I discovered "syncthing" via this thread and while it sucks that I did not come across it before, I am excited …

It was a ton of fun on a saturday afternoon when I wrote this code. I was trying to avoid rolling my own syncing solution but I guess my Google-fu failed me :) My goal was to write…

Thanks for the tip. I wanted to keep my implementation extremely bare-bones and simple so I chose to leave conflict resolution (which itself is a rare event in my a use-case as I u…

It is based on Git so uses the same mechanism. When a merge cannot be done because of conflict, you can resolve in the usual git workflow.

This looks just perfect. Trying it out.

I tried using Sparkleshare. It was buggy and kept crashing after being unresponsive. When I checked the repo, I found that there wasn't much activity.

Very cool! I wish I'd found your repo before writing my implementation. In fact, I was going to rewrite mine in Golang to reduce memory consumption on my back-up server. I will tak…

Nice! I wish they support fetching changes from the remote repo upon an file change event. I'd written a dropbox equivalent using git as the storage mechanism that does something s…