all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pascal Bourguignon <pjb@informatimago.com>
To: help-gnu-emacs@gnu.org
Subject: Re: distributed revision control?
Date: Sun, 05 Aug 2007 14:12:50 +0200	[thread overview]
Message-ID: <87lkcq2n99.fsf@voyager.informatimago.com> (raw)
In-Reply-To: 1186283558.939662.293950@e16g2000pri.googlegroups.com

knubee <knubee@gmail.com> writes:

> A colleague and I want to work on some shared documents via tramp and
> revision control. The issue: we do not have access to a shared
> location that could serve as a centralized repository. (Our project
> isn't an open source software project and doesn't warrant such things
> as sourceforge etc. We tried google projects but couldn't see a way to
> integrate this with emacs version control.)
>
> Reading about "distributed revision control systems" (DRCS) suggests
> this may be the way to go. However, most of the information we have
> found suggests that although individuals can work independently on
> their local versions, there is an assumption that at some point
> changes are committed to a single repository.
>
> The model we would like to pursue is that the local version of one of
> us exists as the main repository. So, one approach is" "committing" to
> that repository would take the form of something more like email than
> ftp/ssh access to a machine with a repository. (We are also open to
> other approaches)
>
> Does anyone here know if Arch or Bazaar-NG (or something else we could
> use from within emacs) support such a model? If so, any pointers to
> how to do this?
>
> (Sorry if this post is off topic. If there is a more appropriate list
> that deals with revision control systems available within emacs,
> please let me know.)
>
> thanks.
>

darcs is designed to deal with this problem.  Technically, there is no
central repository in darcs, all the sandboxes are branches.

Changes are not commited to any central repository, but at one point,
you may want to send your patches to the other guys, and vice versa.
If you're only two, it's ok; if you're more, it's easier if there is a
single central integrator.


-- 
__Pascal Bourguignon__                     http://www.informatimago.com/

THIS IS A 100% MATTER PRODUCT: In the unlikely event that this
merchandise should contact antimatter in any form, a catastrophic
explosion will result.

  reply	other threads:[~2007-08-05 12:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05  3:12 distributed revision control? knubee
2007-08-05 12:12 ` Pascal Bourguignon [this message]
2007-08-05 13:01   ` knubee
2007-08-07 10:50   ` Tim X
2007-08-07 11:05     ` Harald Hanche-Olsen
2007-08-05 17:06 ` Giorgos Keramidas
2007-08-06 13:59   ` knubee
2007-08-06 14:31 ` Edward O'Connor
     [not found] ` <mailman.4437.1186410707.32220.help-gnu-emacs@gnu.org>
2007-08-07 14:32   ` knubee
2007-08-07 14:44     ` Hadron
2007-08-11  1:38 ` der-mustermann

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

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

  git send-email \
    --in-reply-to=87lkcq2n99.fsf@voyager.informatimago.com \
    --to=pjb@informatimago.com \
    --cc=help-gnu-emacs@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.