From: Thorsten Jolitz <tjolitz@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: Re: How to deal with small projects which are often changing their status/ person
Date: Tue, 22 Jan 2013 22:56:38 +0100 [thread overview]
Message-ID: <871udcanl5.fsf@googlemail.com> (raw)
In-Reply-To: 87sj5szyl4.fsf@yahoo.fr
"Nicolas Richard" <theonewiththeevillook@yahoo.fr> writes:
> 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).
Thats a nice way to enable Emacs/Org-mode/Magit users to work with
fellows from the Microsoft universe - thanks for the tip.
--
cheers,
Thorsten
next prev parent reply other threads:[~2013-01-22 21:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 20:19 How to deal with small projects which are often changing their status/ person M
2013-01-22 21:14 ` Thorsten Jolitz
2013-01-22 21:39 ` Nicolas Richard
2013-01-22 21:56 ` Thorsten Jolitz [this message]
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871udcanl5.fsf@googlemail.com \
--to=tjolitz@googlemail.com \
--cc=emacs-orgmode@gnu.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).