[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] How to deal with small projects which are often changing their s
From: |
Nicolas Richard |
Subject: |
Re: [O] How to deal with small projects which are often changing their status/ person |
Date: |
Tue, 22 Jan 2013 22:39:51 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.2.92 (gnu/linux) |
Thorsten Jolitz <address@hidden> writes:
> If you/your fellow workers don't use GIT or another VCS, there is still
> dropbox - put your project text files in your dropbox folder and share
> them with other, there are automatic backups of older versions by
> Dropbox.
I use one trick which might be of interest to some people : when I have
a dropbox folder with text (in my case, these are .tex and related
files) files that will be worked on collaboratively, I first follow
these steps in the directory :
dropbox exclude add .git
git init
git add .
git commit -m "Initial commit"
(it is important that the first step comes first, this avoids the .git
directory from being synched to everyone sharing the folder)
>From that moment on, I can monitor changes using git diff which I find
much easier (in particular thank to magit) than Dropbox's own
facilities. Everytime there are new chages, I usually commit them in
order to have some history saved locally (though less complete than the
history in dropbox, since I probably won't commit after every single
change).
(As a side note : another way to use git + dropbox is to have your .git
directory sync'd between your different computers, but I don't like this
very much, and obviously this would be for a completely different
purpose.)
--
Nico.