Org-mode mailing list
 help / color / mirror / Atom feed
From: M <>
To: Thorsten Jolitz <>,
Subject: Re: How to deal with small projects which are often changing their status/ person
Date: Tue, 22 Jan 2013 22:40:29 +0100
Message-ID: <> (raw)
In-Reply-To: <>

Thanks Thorsten for your reply!

it is not about programming and it is not about plain text files, but MS
Office (Word) files..

Dropbox is not an option, maybe a document management system (DMS) with
versioning, but it is not in place yet.
And even if there is, how could  I then track my workflow with Emacs?

Kind regards


> Von: Thorsten Jolitz <>
> Datum: Tue, 22 Jan 2013 22:14:42 +0100
> An: <>
> Betreff: Re: [O] How to deal with small projects which are often changing
> their status/ person
> M <> writes:
> Hi, 
>> At the moment there are many little projects where I
>> * get a text from someone (or write it myself)
>> * have to read and edit it
>> * send it oer email to 1 or 2 other colleagues which have to read / edit it
>> * get it back and check the changes
>> * maybe send the text again to the original author
>> * then finally release the text for publication
>> ... and you imagine, there is not only 1 such text at once but several of
>> them.
>> I wonder what is an approriate way to keep track of such workflows with
>> org-mode..
> this doesn't sound so different from several programmers working on the
> same source code file, so I suspect that GIT is the best and the most
> popular solution for collaborative work on plain text files.
> 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. 
> Or you wait for colorg to be released, that would probably fit your
> needs exactly 
> -- 
> cheers,
> Thorsten

  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
2013-01-22 21:56     ` Thorsten Jolitz
2013-01-22 21:40   ` M [this message]
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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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 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/ \
	public-inbox-index list

Example config snippet for mirrors.
Newsgroups are available over NNTP:

AGPL code for this site: git clone