From: "Nicolas Richard" <firstname.lastname@example.org> To: email@example.com Subject: Re: How to deal with small projects which are often changing their status/ person Date: Tue, 22 Jan 2013 22:39:51 +0100 Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Thorsten Jolitz <firstname.lastname@example.org> 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.
next prev parent reply other threads:[~2013-01-22 21:40 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-22 20:19 M 2013-01-22 21:14 ` Thorsten Jolitz 2013-01-22 21:39 ` Nicolas Richard [this message] 2013-01-22 21:56 ` Thorsten Jolitz 2013-01-22 21:40 ` M 2013-01-22 21:55 ` Thorsten Jolitz 2013-01-23 8:59 ` Tomas Hlavaty 2013-01-23 10:20 ` OT: using ZIP based files with git (was: How to deal with small projects which are often changing their status/ person) Karl Voit 2013-01-22 21:39 ` How to deal with small projects which are often changing their status/ person Thomas S. Dye 2013-01-22 22:27 ` M 2013-01-22 22:49 ` Thomas S. Dye 2013-01-23 1:59 ` Eric Abrahamsen 2013-01-23 9:15 ` Julian Burgos
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://orgmode.org * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Org-mode mailing list This inbox may be cloned and mirrored by anyone: git clone --mirror https://orgmode.org/list/0 list/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 list list/ https://orgmode.org/list \ firstname.lastname@example.org public-inbox-index list Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.yhetil.org/yhetil.emacs.orgmode nntp://news.gmane.io/gmane.emacs.orgmode AGPL code for this site: git clone https://public-inbox.org/public-inbox.git