Hi Theo,
Thanks for the tip. I don't really program in bash, so that was a
useful tip. I'll start getting into it more, as it's a simple and
powerful way to solve problems, and it's available almost everywhere
you have a POSIX OS :)
Cheers,
Marcelo.
On Mon, May 2, 2011 at 12:16 PM, theo wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
On 01/05/2011 07:36, Marcelo de Moraes Serpa wrote:
>
> 1 DAYW=$(date | cut -d" " -f 1)
> 2 NOW=$(date +"%d-%m-%Y-%r")
> [...]
> 6 git commit -a -m "$DAYW-$NOW"
Could be shorten :
6 git commit -a -m "$(date +'%A-%F-%T')"
- --
Fr
Bernt,
That's amazing!
Much more complex, and I really liked the idea of tracking every
directory that has important files (including configuration files).
Thank you for sharing.
As for deleting files, I just rm -rf when I need to, so the next
commit -a will catch it.
But yours is definitely a
Marcelo de Moraes Serpa writes:
> Another thing: I'm considering setting the commit cron job to every
> hour. So, every hour I would have a fresh copy of org pushed to my
> dropbox volume.
>
> I forgot to share the commit.sh (I don't usually program in bash, so
> bear with me :)):
>
> 1 DAYW=$
Another thing: I'm considering setting the commit cron job to every
hour. So, every hour I would have a fresh copy of org pushed to my
dropbox volume.
I forgot to share the commit.sh (I don't usually program in bash, so
bear with me :)):
1 DAYW=$(date | cut -d" " -f 1)
2 NOW=$(date +"%d-%m-%
Hi list,
I just would like to share the approach I use (just finished setting
it up) to backup org.
I keep all my org files on ~/org/*. This is also a git repo. Every
night at 12:00AM, a cron job will run a sh script that will:
1) Commit with the current date ( Sat-30-04-2011-11:43:28 PM for exa
